[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGQ4Y0HHZTA1ZJ1R52MPVC":3,"skill-same:01M6EGQ4Y0HHZTA1ZJ1R52MPVC":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6EGQ4Y0HHZTA1ZJ1R52MPVC","ln-910-community-engagement",null,"Community engagement coordinator: analyzes repo health, consults strategy, delegates to announcer\u002Fdebater\u002Ftriager","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-910-community-engagement\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"engagement","community","community engagement","ln 910 community engagement","health","Bash","grep","repo","read","strategy","2026-11-10 10:12:30",false,"---\nname: ln-910-community-engagement\ndescription: \"Community engagement coordinator: analyzes repo health, consults strategy, delegates to announcer\u002Fdebater\u002Ftriager\"\nlicense: MIT\nallowed-tools: Read, Grep, Glob, Bash, Skill\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# ln-910-community-engagement\n\n**Type:** L2 Coordinator (active)\n**Category:** 9XX Community Engagement\n\nAnalyzes current community health and repository state, consults the engagement strategy, and delegates to the appropriate worker. Each worker is also invocable standalone.\n\n---\n\n## Overview\n\n| Aspect | Details |\n|--------|---------|\n| **Input** | `$ARGUMENTS` (optional): topic, action keyword, or empty for auto-analysis |\n| **Output** | Situation report + delegated action via worker skill |\n| **Workers** | ln-911 (triager), ln-912 (announcer), ln-913 (debater) |\n\n---\n\n## Phase 0: GitHub Discovery\n\n**MANDATORY READ:** Load `references\u002Fgithub_discovery.md`\n\nExecute the discovery protocol. Extract:\n- `{owner}\u002F{repo}` for all GitHub operations\n- `repo.id` for GraphQL mutations (passed to workers)\n- `maintainer` login (authenticated user)\n- Discussion category IDs\n\n**Gate checks:** gh authenticated? Discussions enabled?\n\nLoad strategy: check `docs\u002Fcommunity_engagement_strategy.md` in target project, fallback to `references\u002Fcommunity_strategy_template.md`.\n\n---\n\n## Phase 1: Situation Analysis\n\nIf `$ARGUMENTS` contains a direct action keyword (`announce`, `debate`, `triage`), skip analysis and jump to Phase 3 (Direct Delegation).\n\nOtherwise, gather context from multiple sources in parallel:\n\n### 1a. Community Health\n\nDelegate to triager in summary mode (no interactive preview):\n\n`Skill(skill: \"ln-911-github-triager\", args: \"summary\")`\n\nExtract from triager output: red flags, priority counts (P0\u002FP1\u002FP2), health metrics.\n\n### 1b. Unreleased Changes\n\n```bash\n# Last announcement date: most recent Announcements discussion\ngh api graphql -f query='query($owner: String!, $name: String!) {\n  repository(owner: $owner, name: $name) {\n    discussions(first: 1, categoryId: \"{categories.Announcements}\", orderBy: {field: CREATED_AT, direction: DESC}) {\n      nodes { createdAt title }\n    }\n  }\n}' -f owner=\"{owner}\" -f name=\"{repo}\"\n```\n\nThen check what changed since:\n```bash\ngit log --oneline --since=\"{last_announcement_date}\"\n```\n\nRead `CHANGELOG.md` — any entries newer than the last announcement?\n\n### 1c. Cadence Check\n\nFrom strategy Section 4:\n- Days since last announcement → monthly digest overdue if >30 days?\n- Any pending architectural decisions that need RFC?\n\n---\n\n## Phase 2: Decision Matrix\n\nApply strategy Section 1 (Announcement vs Debate) to the gathered context:\n\n| Condition | Priority | Action | Worker |\n|-----------|----------|--------|--------|\n| Red flags: unanswered discussions >7d | **P0** | List items needing response (no worker — direct action) | Recommendations only |\n| Red flags: PRs needing review | **P0** | List PRs needing review | Recommendations only |\n| Unreleased changes in CHANGELOG | **P1** | Announce: new features\u002Ffixes | → ln-912 |\n| `$ARGUMENTS` contains RFC\u002Fdebate topic | **P1** | Debate: launch RFC | → ln-913 |\n| Monthly digest overdue (>30d) | **P2** | Monthly digest announcement | → ln-912 |\n| Design questions identified in Phase 1 | **P2** | Debate: RFC for open decisions | → ln-913 |\n| Community health OK, nothing unreleased | **—** | Report \"all clear\" | No delegation |\n\n### Output: Situation Report\n\nPresent to user:\n\n```\n## Community Status — {YYYY-MM-DD}\n\n**Repo:** {owner}\u002F{repo}\n**Last announcement:** {date} ({days} days ago)\n**Open items:** {issues} issues, {prs} PRs, {discussions} discussions\n\n### Red Flags\n{list or \"None\"}\n\n### Recommended Action\n{One of: Announce \u002F Debate \u002F Respond to items \u002F No action needed}\n\n**Reason:** {brief explanation based on strategy criteria}\n```\n\n**Wait for user approval before proceeding.**\n\n---\n\n## Phase 3: Delegate\n\nAfter user approves the recommended action:\n\n### Direct Delegation (when `$ARGUMENTS` specifies action)\n\n| Argument | Delegation |\n|----------|-----------|\n| `announce` or `announce {topic}` | `Skill(skill: \"ln-912-community-announcer\", args: \"{topic}\")` |\n| `debate` or `debate {topic}` | `Skill(skill: \"ln-913-community-debater\", args: \"{topic}\")` |\n| `triage` or `triage {scope}` | `Skill(skill: \"ln-911-github-triager\", args: \"{scope}\")` |\n\n### Analysis-Based Delegation\n\n| Recommended action | Delegation |\n|-------------------|-----------|\n| Announce | `Skill(skill: \"ln-912-community-announcer\")` — worker gathers its own context |\n| Debate | `Skill(skill: \"ln-913-community-debater\", args: \"{identified topic}\")` |\n| Respond to items | No delegation — present the list of items needing response with GitHub URLs |\n| No action needed | Report status, done |\n\n---\n\n## Shared References\n\n| File | Purpose |\n|------|---------|\n| `references\u002Fgithub_discovery.md` | Phase 0: dynamic repo\u002Fcategory\u002Fuser discovery |\n| `references\u002Fcommunity_strategy_template.md` | Default engagement strategy (fallback) |\n| `references\u002Fdiscussion_formatting.md` | GitHub Discussion formatting rules |\n\n---\n\n## Strategy Override\n\nEach target project can override the default strategy by creating `docs\u002Fcommunity_engagement_strategy.md`. All skills check project-local first, then fall back to the template in `references\u002F`.\n\n---\n\n## Definition of Done\n\n- [ ] GitHub discovery complete (owner\u002Frepo, categories, maintainer extracted)\n- [ ] Situation analyzed (health + unreleased changes + cadence) OR direct delegation triggered\n- [ ] Decision matrix applied with priority-based action selection\n- [ ] Worker delegated or recommendations shown to user\n- [ ] User informed of outcome\n\n---\n\n## Phase 4: Meta-Analysis\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fmeta_analysis_protocol.md`\n\nSkill type: `planning-coordinator`. Run after Phase 3 completes. Output to chat using the `planning-coordinator` format.\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# ln-910-community-engagement\n\n**Type:** L2 Coordinator (active)\n**Category:** 9XX Community Engagement\n\nAnalyzes current community health and repository state, consults the engagement strategy, and delegates to the appropriate worker. Each worker is also invocable standalone.\n\n---\n\n## Overview\n\n| Aspect | Details |\n|--------|---------|\n| **Input** | `$ARGUMENTS` (optional): topic, action keyword, or empty for auto-analysis |\n| **Output** | Situation report + delegated action via worker skill |\n| **Workers** | ln-911 (triager), ln-912 (announcer), ln-913 (debater) |\n\n---\n\n## Phase 0: GitHub Discovery\n\n**MANDATORY READ:** Load `references\u002Fgithub_discovery.md`\n\nExecute the discovery protocol. Extract:\n- `{owner}\u002F{repo}` for all GitHub operations\n- `repo.id` for GraphQL mutations (passed to workers)\n- `maintainer` login (authenticated user)\n- Discussion category IDs\n\n**Gate checks:** gh authenticated? Discussions enabled?\n\nLoad strategy: check `docs\u002Fcommunity_engagement_strategy.md` in target project, fallback to `references\u002Fcommunity_strategy_template.md`.\n\n---\n\n## Phase 1: Situation Analysis\n\nIf `$ARGUMENTS` contains a direct action keyword (`announce`, `debate`, `triage`), skip analysis and jump to Phase 3 (Direct Delegation).\n\nOtherwise, gather context from multiple sources in parallel:\n\n### 1a. Community Health\n\nDelegate to triager in summary mode (no interactive preview):\n\n`Skill(skill: \"ln-911-github-triager\", args: \"summary\")`\n\nExtract from triager output: red flags, priority counts (P0\u002FP1\u002FP2), health metrics.\n\n### 1b. Unreleased Changes\n\n```bash\n# Last announcement date: most recent Announcements discussion\ngh api graphql -f query='query($owner: String!, $name: String!) {\n  repository(owner: $owner, name: $name) {\n    discussions(first: 1, categoryId: \"{categories.Announcements}\", orderBy: {field: CREATED_AT, direction: DESC}) {\n      nodes { createdAt title }\n    }\n  }\n}' -f owner=\"{owner}\" -f name=\"{repo}\"\n```\n\nThen check what changed since:\n```bash\ngit log --oneline --since=\"{last_announcement_date}\"\n```\n\nRead `CHANGELOG.md` — any entries newer than the last announcement?\n\n### 1c. Cadence Check\n\nFrom strategy Section 4:\n- Days since last announcement → monthly digest overdue if >30 days?\n- Any pending architectural decisions that need RFC?\n\n---\n\n## Phase 2: Decision Matrix\n\nApply strategy Section 1 (Announcement vs Debate) to the gathered context:\n\n| Condition | Priority | Action | Worker |\n|-----------|----------|--------|--------|\n| Red flags: unanswered discussions >7d | **P0** | List items needing response (no worker — direct action) | Recommendations only |\n| Red flags: PRs needing review | **P0** | List PRs needing review | Recommendations only |\n| Unreleased changes in CHANGELOG | **P1** | Announce: new features\u002Ffixes | → ln-912 |\n| `$ARGUMENTS` contains RFC\u002Fdebate topic | **P1** | Debate: launch RFC | → ln-913 |\n| Monthly digest overdue (>30d) | **P2** | Monthly digest announcement | → ln-912 |\n| Design questions identified in Phase 1 | **P2** | Debate: RFC for open decisions | → ln-913 |\n| Community health OK, nothing unreleased | **—** | Report \"all clear\" | No delegation |\n\n### Output: Situation Report\n\nPresent to user:\n\n```\n## Community Status — {YYYY-MM-DD}\n\n**Repo:** {owner}\u002F{repo}\n**Last announcement:** {date} ({days} days ago)\n**Open items:** {issues} issues, {prs} PRs, {discussions} discussions\n\n### Red Flags\n{list or \"None\"}\n\n### Recommended Action\n{One of: Announce \u002F Debate \u002F Respond to items \u002F No action needed}\n\n**Reason:** {brief explanation based on strategy criteria}\n```\n\n**Wait for user approval before proceeding.**\n\n---\n\n## Phase 3: Delegate\n\nAfter user approves the recommended action:\n\n### Direct Delegation (when `$ARGUMENTS` specifies action)\n\n| Argument | Delegation |\n|----------|-----------|\n| `announce` or `announce {topic}` | `Skill(skill: \"ln-912-community-announcer\", args: \"{topic}\")` |\n| `debate` or `debate {topic}` | `Skill(skill: \"ln-913-community-debater\", args: \"{topic}\")` |\n| `triage` or `triage {scope}` | `Skill(skill: \"ln-911-github-triager\", args: \"{scope}\")` |\n\n### Analysis-Based Delegation\n\n| Recommended action | Delegation |\n|-------------------|-----------|\n| Announce | `Skill(skill: \"ln-912-community-announcer\")` — worker gathers its own context |\n| Debate | `Skill(skill: \"ln-913-community-debater\", args: \"{identified topic}\")` |\n| Respond to items | No delegation — present the list of items needing response with GitHub URLs |\n| No action needed | Report status, done |\n\n---\n\n## Shared References\n\n| File | Purpose |\n|------|---------|\n| `references\u002Fgithub_discovery.md` | Phase 0: dynamic repo\u002Fcategory\u002Fuser discovery |\n| `references\u002Fcommunity_strategy_template.md` | Default engagement strategy (fallback) |\n| `references\u002Fdiscussion_formatting.md` | GitHub Discussion formatting rules |\n\n---\n\n## Strategy Override\n\nEach target project can override the default strategy by creating `docs\u002Fcommunity_engagement_strategy.md`. All skills check project-local first, then fall back to the template in `references\u002F`.\n\n---\n\n## Definition of Done\n\n- [ ] GitHub discovery complete (owner\u002Frepo, categories, maintainer extracted)\n- [ ] Situation analyzed (health + unreleased changes + cadence) OR direct delegation triggered\n- [ ] Decision matrix applied with priority-based action selection\n- [ ] Worker delegated or recommendations shown to user\n- [ ] User informed of outcome\n\n---\n\n## Phase 4: Meta-Analysis\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Fmeta_analysis_protocol.md`\n\nSkill type: `planning-coordinator`. Run after Phase 3 completes. Output to chat using the `planning-coordinator` format.\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-03-13\n",{"name":5,"license":15,"description":7,"allowed-tools":34},"Read, Grep, Glob, Bash, Skill","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-910-community-engagement",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-910-community-engagement",{"tool":50,"command":51},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-910-community-engagement",{"tool":53,"command":54},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-910-community-engagement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-910-community-engagement\u002FSKILL.md",true,[58,64,68],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcommunity_strategy_template.md","REFERENCE","参考文档",5753,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-910-community-engagement\u002Freferences\u002Fcommunity_strategy_template.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fdiscussion_formatting.md",3242,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-910-community-engagement\u002Freferences\u002Fdiscussion_formatting.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fgithub_discovery.md",2439,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-910-community-engagement\u002Freferences\u002Fgithub_discovery.md",[73,95,133,160,186,214],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":29},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":114,"publishedAt":29},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[101,106,109],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[97,80,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":29},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":29},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[167,168,169,170,171,172,173,174,175,176,177,178,123,179,180,181,182,183,184,185],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":195,"publishedAt":29},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[192],{"categoryNo":193,"categoryName":194,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000009","前端开发",[196,197,198,199,200,201,202,203,204,205,206,207,208,118,209,210,211,212,213,128],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":230,"publishedAt":29},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[220,223,226,227],{"categoryNo":221,"categoryName":222,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":224,"categoryName":225,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":107,"categoryName":108,"taxonomyType":104,"taxonomyTypeDesc":105},{"categoryNo":228,"categoryName":229,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者",[119,231,232,205,233,234,235,236,24,237,27,151,238,239,240,241,242,243,94,244],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","requirements","formatting","journal","chi"]