[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ED2FHC58FPB86TAJ6RJ4N1":3,"skill-same:01M6ED2FHC58FPB86TAJ6RJ4N1":88},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6ED2FHC58FPB86TAJ6RJ4N1","c-level-advisor",null,"Provides strategic business advice by channelling the perspectives of 10 executive roles — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, and Executive Mentor — across decisions, trade-offs, and org challenges. Runs multi-role board meetings, routes questions to the right executive voice, and delivers structured recommendations (Bottom Line → What → Why → How to Act → Your Decision). Use when a founder or executive needs business strategy advice, leadership perspective, executive decision support, board-level input, fundraising guidance, product-market fit review, hiring or culture frameworks, risk assessment, or competitive analysis.","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\u002Fc-level-advisor-bundle\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"c level advisor","advisor","how to","review","line","act","recommendations","leadership","across","business strategy","culture","perspectives","decision","why","how","analysis","product","assessment","risk assessment","support","2026-11-10 10:12:30",false,"---\nname: \"c-level-advisor\"\ndescription: \"Provides strategic business advice by channelling the perspectives of 10 executive roles — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, and Executive Mentor — across decisions, trade-offs, and org challenges. Runs multi-role board meetings, routes questions to the right executive voice, and delivers structured recommendations (Bottom Line → What → Why → How to Act → Your Decision). Use when a founder or executive needs business strategy advice, leadership perspective, executive decision support, board-level input, fundraising guidance, product-market fit review, hiring or culture frameworks, risk assessment, or competitive analysis.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: executive-advisory\n  updated: 2026-03-05\n  skills_count: 28\n  scripts_count: 25\n  references_count: 52\n---\n\n# C-Level Advisory Ecosystem\n\nA complete virtual board of directors for founders and executives.\n\n## Quick Start\n\n```\n1. Run \u002Fcs:setup → creates company-context.md (all agents read this)\n   ✓ Verify company-context.md was created and contains your company name,\n     stage, and core metrics before proceeding.\n2. Ask any strategic question → Chief of Staff routes to the right role\n3. For big decisions → \u002Fcs:board triggers a multi-role board meeting\n   ✓ Confirm at least 3 roles have weighed in before accepting a conclusion.\n```\n\n### Commands\n\n#### `\u002Fcs:setup` — Onboarding Questionnaire\n\nWalks through the following prompts and writes `company-context.md` to the project root. Run once per company or when context changes significantly.\n\n```\nQ1. What is your company name and one-line description?\nQ2. What stage are you at? (Idea \u002F Pre-seed \u002F Seed \u002F Series A \u002F Series B+)\nQ3. What is your current ARR (or MRR) and runway in months?\nQ4. What is your team size and structure?\nQ5. What industry and customer segment do you serve?\nQ6. What are your top 3 priorities for the next 90 days?\nQ7. What is your biggest current risk or blocker?\n```\n\nAfter collecting answers, the agent writes structured output:\n\n```markdown\n# Company Context\n- Name: \u003Canswer>\n- Stage: \u003Canswer>\n- Industry: \u003Canswer>\n- Team size: \u003Canswer>\n- Key metrics: \u003CARR\u002FMRR, growth rate, runway>\n- Top priorities: \u003Canswer>\n- Key risks: \u003Canswer>\n```\n\n#### `\u002Fcs:board` — Full Board Meeting\n\nConvenes all relevant executive roles in three phases:\n\n```\nPhase 1 — Framing:   Chief of Staff states the decision and success criteria.\nPhase 2 — Isolation: Each role produces independent analysis (no cross-talk).\nPhase 3 — Debate:    Roles surface conflicts, stress-test assumptions, align on\n                     a recommendation. Dissenting views are preserved in the log.\n```\n\nUse for high-stakes or cross-functional decisions. Confirm at least 3 roles have weighed in before accepting a conclusion.\n\n### Chief of Staff Routing Matrix\n\nWhen a question arrives without a role prefix, the Chief of Staff maps it to the appropriate executive using these primary signals:\n\n| Topic Signal | Primary Role | Supporting Roles |\n|---|---|---|\n| Fundraising, valuation, burn | CFO | CEO, CRO |\n| Architecture, build vs. buy, tech debt | CTO | CPO, CISO |\n| Hiring, culture, performance | CHRO | CEO, Executive Mentor |\n| GTM, demand gen, positioning | CMO | CRO, CPO |\n| Revenue, pipeline, sales motion | CRO | CMO, CFO |\n| Security, compliance, risk | CISO | CTO, CFO |\n| Product roadmap, prioritisation | CPO | CTO, CMO |\n| Ops, process, scaling | COO | CFO, CHRO |\n| Vision, strategy, investor relations | CEO | Executive Mentor |\n| Career, founder psychology, leadership | Executive Mentor | CEO, CHRO |\n| Multi-domain \u002F unclear | Chief of Staff convenes board | All relevant roles |\n\n### Invoking a Specific Role Directly\n\nTo bypass Chief of Staff routing and address one executive directly, prefix your question with the role name:\n\n```\nCFO: What is our optimal burn rate heading into a Series A?\nCTO: Should we rebuild our auth layer in-house or buy a solution?\nCHRO: How do we design a performance review process for a 15-person team?\n```\n\nThe Chief of Staff still logs the exchange; only routing is skipped.\n\n### Example: Strategic Question\n\n**Input:** \"Should we raise a Series A now or extend runway and grow ARR first?\"\n\n**Output format:**\n- **Bottom Line:** Extend runway 6 months; raise at $2M ARR for better terms.\n- **What:** Current $800K ARR is below the threshold most Series A investors benchmark.\n- **Why:** Raising now increases dilution risk; 6-month extension is achievable with current burn.\n- **How to Act:** Cut 2 low-ROI channels, hit $2M ARR, then run a 6-week fundraise sprint.\n- **Your Decision:** Proceed with extension \u002F Raise now anyway (choose one).\n\n### Example: company-context.md (after \u002Fcs:setup)\n\n```markdown\n# Company Context\n- Name: Acme Inc.\n- Stage: Seed ($800K ARR)\n- Industry: B2B SaaS\n- Team size: 12\n- Key metrics: 15% MoM growth, 18-month runway\n- Top priorities: Series A readiness, enterprise GTM\n```\n\n## What's Included\n\n### 10 C-Suite Roles\nCEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor\n\n### 6 Orchestration Skills\nFounder Onboard, Chief of Staff (router), Board Meeting, Decision Logger, Agent Protocol, Context Engine\n\n### 6 Cross-Cutting Capabilities\nBoard Deck Builder, Scenario War Room, Competitive Intel, Org Health Diagnostic, M&A Playbook, International Expansion\n\n### 6 Culture & Collaboration\nCulture Architect, Company OS, Founder Coach, Strategic Alignment, Change Management, Internal Narrative\n\n## Key Features\n\n- **Internal Quality Loop:** Self-verify → peer-verify → critic pre-screen → present\n- **Two-Layer Memory:** Raw transcripts + approved decisions only (prevents hallucinated consensus)\n- **Board Meeting Isolation:** Phase 2 independent analysis before cross-examination\n- **Proactive Triggers:** Context-driven early warnings without being asked\n- **Structured Output:** Bottom Line → What → Why → How to Act → Your Decision\n- **25 Python Tools:** All stdlib-only, CLI-first, JSON output, zero dependencies\n\n## See Also\n\n- `CLAUDE.md` — full architecture diagram and integration guide\n- `agent-protocol\u002FSKILL.md` — communication standard and quality loop details\n- `chief-of-staff\u002FSKILL.md` — routing matrix for all 28 skills\n","# C-Level Advisory Ecosystem\n\nA complete virtual board of directors for founders and executives.\n\n## Quick Start\n\n```\n1. Run \u002Fcs:setup → creates company-context.md (all agents read this)\n   ✓ Verify company-context.md was created and contains your company name,\n     stage, and core metrics before proceeding.\n2. Ask any strategic question → Chief of Staff routes to the right role\n3. For big decisions → \u002Fcs:board triggers a multi-role board meeting\n   ✓ Confirm at least 3 roles have weighed in before accepting a conclusion.\n```\n\n### Commands\n\n#### `\u002Fcs:setup` — Onboarding Questionnaire\n\nWalks through the following prompts and writes `company-context.md` to the project root. Run once per company or when context changes significantly.\n\n```\nQ1. What is your company name and one-line description?\nQ2. What stage are you at? (Idea \u002F Pre-seed \u002F Seed \u002F Series A \u002F Series B+)\nQ3. What is your current ARR (or MRR) and runway in months?\nQ4. What is your team size and structure?\nQ5. What industry and customer segment do you serve?\nQ6. What are your top 3 priorities for the next 90 days?\nQ7. What is your biggest current risk or blocker?\n```\n\nAfter collecting answers, the agent writes structured output:\n\n```markdown\n# Company Context\n- Name: \u003Canswer>\n- Stage: \u003Canswer>\n- Industry: \u003Canswer>\n- Team size: \u003Canswer>\n- Key metrics: \u003CARR\u002FMRR, growth rate, runway>\n- Top priorities: \u003Canswer>\n- Key risks: \u003Canswer>\n```\n\n#### `\u002Fcs:board` — Full Board Meeting\n\nConvenes all relevant executive roles in three phases:\n\n```\nPhase 1 — Framing:   Chief of Staff states the decision and success criteria.\nPhase 2 — Isolation: Each role produces independent analysis (no cross-talk).\nPhase 3 — Debate:    Roles surface conflicts, stress-test assumptions, align on\n                     a recommendation. Dissenting views are preserved in the log.\n```\n\nUse for high-stakes or cross-functional decisions. Confirm at least 3 roles have weighed in before accepting a conclusion.\n\n### Chief of Staff Routing Matrix\n\nWhen a question arrives without a role prefix, the Chief of Staff maps it to the appropriate executive using these primary signals:\n\n| Topic Signal | Primary Role | Supporting Roles |\n|---|---|---|\n| Fundraising, valuation, burn | CFO | CEO, CRO |\n| Architecture, build vs. buy, tech debt | CTO | CPO, CISO |\n| Hiring, culture, performance | CHRO | CEO, Executive Mentor |\n| GTM, demand gen, positioning | CMO | CRO, CPO |\n| Revenue, pipeline, sales motion | CRO | CMO, CFO |\n| Security, compliance, risk | CISO | CTO, CFO |\n| Product roadmap, prioritisation | CPO | CTO, CMO |\n| Ops, process, scaling | COO | CFO, CHRO |\n| Vision, strategy, investor relations | CEO | Executive Mentor |\n| Career, founder psychology, leadership | Executive Mentor | CEO, CHRO |\n| Multi-domain \u002F unclear | Chief of Staff convenes board | All relevant roles |\n\n### Invoking a Specific Role Directly\n\nTo bypass Chief of Staff routing and address one executive directly, prefix your question with the role name:\n\n```\nCFO: What is our optimal burn rate heading into a Series A?\nCTO: Should we rebuild our auth layer in-house or buy a solution?\nCHRO: How do we design a performance review process for a 15-person team?\n```\n\nThe Chief of Staff still logs the exchange; only routing is skipped.\n\n### Example: Strategic Question\n\n**Input:** \"Should we raise a Series A now or extend runway and grow ARR first?\"\n\n**Output format:**\n- **Bottom Line:** Extend runway 6 months; raise at $2M ARR for better terms.\n- **What:** Current $800K ARR is below the threshold most Series A investors benchmark.\n- **Why:** Raising now increases dilution risk; 6-month extension is achievable with current burn.\n- **How to Act:** Cut 2 low-ROI channels, hit $2M ARR, then run a 6-week fundraise sprint.\n- **Your Decision:** Proceed with extension \u002F Raise now anyway (choose one).\n\n### Example: company-context.md (after \u002Fcs:setup)\n\n```markdown\n# Company Context\n- Name: Acme Inc.\n- Stage: Seed ($800K ARR)\n- Industry: B2B SaaS\n- Team size: 12\n- Key metrics: 15% MoM growth, 18-month runway\n- Top priorities: Series A readiness, enterprise GTM\n```\n\n## What's Included\n\n### 10 C-Suite Roles\nCEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor\n\n### 6 Orchestration Skills\nFounder Onboard, Chief of Staff (router), Board Meeting, Decision Logger, Agent Protocol, Context Engine\n\n### 6 Cross-Cutting Capabilities\nBoard Deck Builder, Scenario War Room, Competitive Intel, Org Health Diagnostic, M&A Playbook, International Expansion\n\n### 6 Culture & Collaboration\nCulture Architect, Company OS, Founder Coach, Strategic Alignment, Change Management, Internal Narrative\n\n## Key Features\n\n- **Internal Quality Loop:** Self-verify → peer-verify → critic pre-screen → present\n- **Two-Layer Memory:** Raw transcripts + approved decisions only (prevents hallucinated consensus)\n- **Board Meeting Isolation:** Phase 2 independent analysis before cross-examination\n- **Proactive Triggers:** Context-driven early warnings without being asked\n- **Structured Output:** Bottom Line → What → Why → How to Act → Your Decision\n- **25 Python Tools:** All stdlib-only, CLI-first, JSON output, zero dependencies\n\n## See Also\n\n- `CLAUDE.md` — full architecture diagram and integration guide\n- `agent-protocol\u002FSKILL.md` — communication standard and quality loop details\n- `chief-of-staff\u002FSKILL.md` — routing matrix for all 28 skills\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"skills_count":50,"scripts_count":51,"references_count":52},"Alireza Rezvani","executive-advisory",1772668800000,"2.0.0","c-level",28,25,52,"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fc-level-advisor-bundle",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add levalencia\u002Fagent-god-mode --skill c-level-advisor",{"tool":68,"command":69},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill c-level-advisor",{"tool":71,"command":72},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill c-level-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fc-level-advisor-bundle\u002FSKILL.md",true,[76,82],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"agents\u002Fopenai.yaml","REFERENCE","参考文档",96,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwizard\u002Fagents\u002Fopenai.yaml",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"template.sh","SCRIPT","脚本",9960,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwizard\u002Ftemplate.sh",[89,111,149,176,200,228],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":39},"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",[],[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":130,"publishedAt":39},"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",[117,122,125],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":123,"categoryName":124,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[113,96,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":39},"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",[],[156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"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":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":39},"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",[],[183,184,185,186,187,188,189,34,190,31,191,192,139,193,194,195,196,197,198,199],"oracle","what if oracle","test","planning","ux","futures","risk","explore","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":209,"publishedAt":39},"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",[206],{"categoryNo":207,"categoryName":208,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000009","前端开发",[210,211,212,213,214,215,216,217,218,219,220,221,222,134,223,224,225,226,227,144],"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":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":244,"publishedAt":39},"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",[234,237,240,241],{"categoryNo":235,"categoryName":236,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":238,"categoryName":239,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":123,"categoryName":124,"taxonomyType":120,"taxonomyTypeDesc":121},{"categoryNo":242,"categoryName":243,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000036","内容创作者",[135,245,246,219,247,248,249,250,251,252,253,167,254,255,256,257,258,259,110,260],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]