[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGFXQDPRN0HE81MQZYFN2B":3,"skill-same:01M6EGFXQDPRN0HE81MQZYFN2B":84},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6EGFXQDPRN0HE81MQZYFN2B","ln-611-docs-structure-auditor",null,"Checks hierarchy & links, SSOT, proactive compression, requirements compliance, freshness indicators, legacy cleanup, stack adaptation. Returns findings with severity, location, and recommendations.","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-611-docs-structure-auditor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"ln 611 docs structure auditor","structure","docs","grep","recommendations","requirements","adaptation","location","Legacy","read","returns","stack","Bash","indicators","severity","compliance","compression","cleanup","2026-11-10 10:12:30",false,"---\nname: ln-611-docs-structure-auditor\ndescription: \"Checks hierarchy & links, SSOT, proactive compression, requirements compliance, freshness indicators, legacy cleanup, stack adaptation. Returns findings with severity, location, and recommendations.\"\nallowed-tools: Read, Grep, Glob, Bash\nlicense: MIT\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# Documentation Structure Auditor (L3 Worker)\n\nSpecialized worker auditing structural quality of project documentation.\n\n## Purpose & Scope\n\n- **Worker in ln-610 coordinator pipeline** - invoked by ln-610-docs-auditor\n- Audit documentation for **structural quality** across 7 categories\n- Scan all `.md` files in project, build hierarchy from CLAUDE.md\n- Return structured findings to coordinator with severity, location, recommendations\n- Calculate compliance score (X\u002F10) for Documentation Structure\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `project_root`, `output_dir`.\n\n## Workflow\n\n1) **Parse Context:** Extract tech stack, project root, output_dir from contextStore\n2) **Scan Docs:** Find all `.md` files in project (CLAUDE.md, README.md, docs\u002F**)\n3) **Build Tree:** Construct hierarchy from CLAUDE.md outward links\n4) **Audit Categories 1-7:** Run structural checks (see Audit Categories below)\n5) **Collect Findings:** Record each violation with severity, location (file:line), effort estimate (S\u002FM\u002FL), recommendation\n6) **Calculate Score:** Count violations by severity, calculate compliance score (X\u002F10)\n7) **Write Report:** Build full markdown report per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F611-structure.md` in single Write call\n8) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Categories\n\n| # | Category | What to Check |\n|---|----------|---------------|\n| 1 | **Hierarchy & Links** | CLAUDE.md is root; all docs reachable via links; no orphaned files; no broken links |\n| 2 | **Single Source of Truth** | No content duplication; duplicates replaced with links to source; clear ownership |\n| 3 | **Proactive Compression** | Eliminate verbose\u002Fredundant content; prose to tables; remove meaningless info; compress even under-limit files; see [size_limits.md](references\u002Fsize_limits.md) |\n| 4 | **Requirements Compliance** | Correct sections; within size limits; **no code blocks** (tables\u002FASCII diagrams\u002Ftext only); stack-appropriate doc links |\n| 5 | **Freshness Indicators** | Detect staleness signals: dates >6 months in content, deprecated API\u002Ftool references, TODO\u002FFIXME markers, placeholder text left in place; deep fact-checking handled by dedicated worker |\n| 6 | **Legacy Cleanup** | No history sections; no \"was changed\" notes; no deprecated info; current state only |\n| 7 | **Stack Adaptation** | Links\u002Frefs match project stack; no Python examples in .NET project; official docs for correct platform |\n\n### Severity Mapping\n\n| Issue Type | Severity |\n|------------|----------|\n| Staleness indicators (old dates, deprecated refs, TODO markers) | MEDIUM |\n| Broken links, orphaned docs | HIGH |\n| Content duplication | MEDIUM |\n| Missing compression opportunity | LOW |\n| Legacy\u002Fhistory content | MEDIUM |\n| Wrong stack references | HIGH |\n\n## Scoring Algorithm\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\n\n## Output Format\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Ftemplates\u002Faudit_worker_report_template.md`.\n\nWrite report to `{output_dir}\u002F611-structure.md` with `category: \"Documentation Structure\"` and checks: hierarchy_links, ssot, compression, requirements_compliance, freshness_indicators, legacy_cleanup, stack_adaptation.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-610\u002F{YYYY-MM-DD}\u002F611-structure.md\nScore: X.X\u002F10 | Issues: N (C:N H:N M:N L:N)\n```\n\n## Critical Rules\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- **Do not auto-fix:** Report violations only; coordinator aggregates for user\n- **Tech stack aware:** Use contextStore `tech_stack` to apply stack-specific checks (e.g., .NET vs Node.js doc standards)\n- **No deep fact-checking:** Detect staleness signals only (dates, deprecated refs, TODO markers)\n- **Compress always:** Size limits are upper bounds, not targets. A 100-line file instead of 300 is a win\n- **No code in docs:** Documents describe algorithms in tables or ASCII diagrams. Code belongs in codebase\n- **Code is truth:** When docs contradict code, report docs as needing update (not code)\n- **Delete, don't archive:** Legacy content should be removed, not moved to \"archive\"\n- **Location precision:** Always include `file:line` for programmatic navigation\n\n## Definition of Done\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- contextStore parsed successfully (including output_dir)\n- All 7 structural categories audited\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F611-structure.md` (atomic single Write call)\n- Summary returned to coordinator\n\n## Reference Files\n\n- Size limits and targets: [references\u002Fsize_limits.md](references\u002Fsize_limits.md)\n- Detailed checklist: [references\u002Faudit_checklist.md](references\u002Faudit_checklist.md)\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-03-01\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# Documentation Structure Auditor (L3 Worker)\n\nSpecialized worker auditing structural quality of project documentation.\n\n## Purpose & Scope\n\n- **Worker in ln-610 coordinator pipeline** - invoked by ln-610-docs-auditor\n- Audit documentation for **structural quality** across 7 categories\n- Scan all `.md` files in project, build hierarchy from CLAUDE.md\n- Return structured findings to coordinator with severity, location, recommendations\n- Calculate compliance score (X\u002F10) for Documentation Structure\n\n## Inputs (from Coordinator)\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\nReceives `contextStore` with: `tech_stack`, `project_root`, `output_dir`.\n\n## Workflow\n\n1) **Parse Context:** Extract tech stack, project root, output_dir from contextStore\n2) **Scan Docs:** Find all `.md` files in project (CLAUDE.md, README.md, docs\u002F**)\n3) **Build Tree:** Construct hierarchy from CLAUDE.md outward links\n4) **Audit Categories 1-7:** Run structural checks (see Audit Categories below)\n5) **Collect Findings:** Record each violation with severity, location (file:line), effort estimate (S\u002FM\u002FL), recommendation\n6) **Calculate Score:** Count violations by severity, calculate compliance score (X\u002F10)\n7) **Write Report:** Build full markdown report per `shared\u002Ftemplates\u002Faudit_worker_report_template.md`, write to `{output_dir}\u002F611-structure.md` in single Write call\n8) **Return Summary:** Return minimal summary to coordinator (see Output Format)\n\n## Audit Categories\n\n| # | Category | What to Check |\n|---|----------|---------------|\n| 1 | **Hierarchy & Links** | CLAUDE.md is root; all docs reachable via links; no orphaned files; no broken links |\n| 2 | **Single Source of Truth** | No content duplication; duplicates replaced with links to source; clear ownership |\n| 3 | **Proactive Compression** | Eliminate verbose\u002Fredundant content; prose to tables; remove meaningless info; compress even under-limit files; see [size_limits.md](references\u002Fsize_limits.md) |\n| 4 | **Requirements Compliance** | Correct sections; within size limits; **no code blocks** (tables\u002FASCII diagrams\u002Ftext only); stack-appropriate doc links |\n| 5 | **Freshness Indicators** | Detect staleness signals: dates >6 months in content, deprecated API\u002Ftool references, TODO\u002FFIXME markers, placeholder text left in place; deep fact-checking handled by dedicated worker |\n| 6 | **Legacy Cleanup** | No history sections; no \"was changed\" notes; no deprecated info; current state only |\n| 7 | **Stack Adaptation** | Links\u002Frefs match project stack; no Python examples in .NET project; official docs for correct platform |\n\n### Severity Mapping\n\n| Issue Type | Severity |\n|------------|----------|\n| Staleness indicators (old dates, deprecated refs, TODO markers) | MEDIUM |\n| Broken links, orphaned docs | HIGH |\n| Content duplication | MEDIUM |\n| Missing compression opportunity | LOW |\n| Legacy\u002Fhistory content | MEDIUM |\n| Wrong stack references | HIGH |\n\n## Scoring Algorithm\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Freferences\u002Faudit_scoring.md`.\n\n## Output Format\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md` and `shared\u002Ftemplates\u002Faudit_worker_report_template.md`.\n\nWrite report to `{output_dir}\u002F611-structure.md` with `category: \"Documentation Structure\"` and checks: hierarchy_links, ssot, compression, requirements_compliance, freshness_indicators, legacy_cleanup, stack_adaptation.\n\nReturn summary to coordinator:\n```\nReport written: docs\u002Fproject\u002F.audit\u002Fln-610\u002F{YYYY-MM-DD}\u002F611-structure.md\nScore: X.X\u002F10 | Issues: N (C:N H:N M:N L:N)\n```\n\n## Critical Rules\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- **Do not auto-fix:** Report violations only; coordinator aggregates for user\n- **Tech stack aware:** Use contextStore `tech_stack` to apply stack-specific checks (e.g., .NET vs Node.js doc standards)\n- **No deep fact-checking:** Detect staleness signals only (dates, deprecated refs, TODO markers)\n- **Compress always:** Size limits are upper bounds, not targets. A 100-line file instead of 300 is a win\n- **No code in docs:** Documents describe algorithms in tables or ASCII diagrams. Code belongs in codebase\n- **Code is truth:** When docs contradict code, report docs as needing update (not code)\n- **Delete, don't archive:** Legacy content should be removed, not moved to \"archive\"\n- **Location precision:** Always include `file:line` for programmatic navigation\n\n## Definition of Done\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Faudit_worker_core_contract.md`.\n\n- contextStore parsed successfully (including output_dir)\n- All 7 structural categories audited\n- Findings collected with severity, location, effort, recommendation\n- Score calculated using penalty algorithm\n- Report written to `{output_dir}\u002F611-structure.md` (atomic single Write call)\n- Summary returned to coordinator\n\n## Reference Files\n\n- Size limits and targets: [references\u002Fsize_limits.md](references\u002Fsize_limits.md)\n- Detailed checklist: [references\u002Faudit_checklist.md](references\u002Faudit_checklist.md)\n\n---\n**Version:** 1.0.0\n**Last Updated:** 2026-03-01\n\n\n",{"name":5,"license":15,"description":7,"allowed-tools":42},"Read, Grep, Glob, Bash","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-611-docs-structure-auditor",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-611-docs-structure-auditor",{"tool":58,"command":59},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-611-docs-structure-auditor",{"tool":61,"command":62},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-611-docs-structure-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-611-docs-structure-auditor\u002FSKILL.md",true,[66,72,76,80],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"evals\u002Fevals.json","REFERENCE","参考文档",6544,"https:\u002F\u002Fgithub.com\u002Fzaka33333-hash\u002Fclaude-skills\u002Fblob\u002Fmain\u002Floose-skills\u002Fcontent-strategy\u002Fevals\u002Fevals.json",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Faudit_checklist.md",8396,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-611-docs-structure-auditor\u002Freferences\u002Faudit_checklist.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fheadless-cms.md",8441,"https:\u002F\u002Fgithub.com\u002Fzaka33333-hash\u002Fclaude-skills\u002Fblob\u002Fmain\u002Floose-skills\u002Fcontent-strategy\u002Freferences\u002Fheadless-cms.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fsize_limits.md",4216,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-611-docs-structure-auditor\u002Freferences\u002Fsize_limits.md",[85,107,145,172,198,226],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":37},"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",[],[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":126,"publishedAt":37},"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",[113,118,121],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":119,"categoryName":120,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[109,92,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":37},"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",[],[152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171],"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":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":37},"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",[],[179,180,181,182,183,184,185,186,187,188,189,190,135,191,192,193,194,195,196,197],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":207,"publishedAt":37},"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",[204],{"categoryNo":205,"categoryName":206,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000009","前端开发",[208,209,210,211,212,213,214,215,216,217,218,219,220,130,221,222,223,224,225,140],"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":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":242,"publishedAt":37},"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",[232,235,238,239],{"categoryNo":233,"categoryName":234,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":236,"categoryName":237,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":119,"categoryName":120,"taxonomyType":116,"taxonomyTypeDesc":117},{"categoryNo":240,"categoryName":241,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000036","内容创作者",[131,243,244,217,245,246,247,248,31,249,28,163,250,251,252,24,253,254,106,255],"venue templates","research","NeurIPS","ICML","LaTeX","science","access","edit","proposals","Academic","formatting","journal","chi"]