[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EB4ZS5DW2173AWR1RQVH1T":3,"skill-same:01M6EB4ZS5DW2173AWR1RQVH1T":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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6EB4ZS5DW2173AWR1RQVH1T","chief-of-staff",null,"C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically.","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\u002F.gemini-chief-of-staff\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"chief of staff","chief","meetings","multi","loads","interaction","founder","triggers","advisor","Synthesis","log","orchestration","context","board","decisions","decision","framework","protocol","routing","2026-11-10 10:12:30",false,"---\nname: \"chief-of-staff\"\ndescription: \"C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: orchestration\n  updated: 2026-03-05\n  frameworks: routing-matrix, synthesis-framework, decision-log, board-protocol\n---\n\n# Chief of Staff\n\nThe orchestration layer between founder and C-suite. Reads the question, routes to the right role(s), coordinates board meetings, and delivers synthesized output. Loads company context for every interaction.\n\n## Keywords\nchief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis\n\n---\n\n## Session Protocol (Every Interaction)\n\n1. Load company context via context-engine skill\n2. Score decision complexity\n3. Route to role(s) or trigger board meeting\n4. Synthesize output\n5. Log decision if reached\n\n---\n\n## Invocation Syntax\n\n```\n[INVOKE:role|question]\n```\n\nExamples:\n```\n[INVOKE:cfo|What's the right runway target given our growth rate?]\n[INVOKE:board|Should we raise a bridge or cut to profitability?]\n```\n\n### Loop Prevention Rules (CRITICAL)\n\n1. **Chief of Staff cannot invoke itself.**\n2. **Maximum depth: 2.** Chief of Staff → Role → stop.\n3. **Circular blocking.** A→B→A is blocked. Log it.\n4. **Board = depth 1.** Roles at board meeting do not invoke each other.\n\nIf loop detected: return to founder with \"The advisors are deadlocked. Here's where they disagree: [summary].\"\n\n---\n\n## Decision Complexity Scoring\n\n| Score | Signal | Action |\n|-------|--------|--------|\n| 1–2 | Single domain, clear answer | 1 role |\n| 3 | 2 domains intersect | 2 roles, synthesize |\n| 4–5 | 3+ domains, major tradeoffs, irreversible | Board meeting |\n\n**+1 for each:** affects 2+ functions, irreversible, expected disagreement between roles, direct team impact, compliance dimension.\n\n---\n\n## Routing Matrix (Summary)\n\nFull rules in `references\u002Frouting-matrix.md`.\n\n| Topic | Primary | Secondary |\n|-------|---------|-----------|\n| Fundraising, burn, financial model | CFO | CEO |\n| Hiring, firing, culture, performance | CHRO | COO |\n| Product roadmap, prioritization | CPO | CTO |\n| Architecture, tech debt | CTO | CPO |\n| Revenue, sales, GTM, pricing | CRO | CFO |\n| Process, OKRs, execution | COO | CFO |\n| Security, compliance, risk | CISO | COO |\n| Company direction, investor relations | CEO | Board |\n| Market strategy, positioning | CMO | CRO |\n| M&A, pivots | CEO | Board |\n\n---\n\n## Board Meeting Protocol\n\n**Trigger:** Score ≥ 4, or multi-function irreversible decision.\n\n```\nBOARD MEETING: [Topic]\nAttendees: [Roles]\nAgenda: [2–3 specific questions]\n\n[INVOKE:role1|agenda question]\n[INVOKE:role2|agenda question]\n[INVOKE:role3|agenda question]\n\n[Chief of Staff synthesis]\n```\n\n**Rules:** Max 5 roles. Each role one turn, no back-and-forth. Chief of Staff synthesizes. Conflicts surfaced, not resolved — founder decides.\n\n---\n\n## Synthesis (Quick Reference)\n\nFull framework in `references\u002Fsynthesis-framework.md`.\n\n1. **Extract themes** — what 2+ roles agree on independently\n2. **Surface conflicts** — name disagreements explicitly; don't smooth them over\n3. **Action items** — specific, owned, time-bound (max 5)\n4. **One decision point** — the single thing needing founder judgment\n\n**Output format:**\n```\n## What We Agree On\n[2–3 consensus themes]\n\n## The Disagreement\n[Named conflict + each side's reasoning + what it's really about]\n\n## Recommended Actions\n1. [Action] — [Owner] — [Timeline]\n...\n\n## Your Decision Point\n[One question. Two options with trade-offs. No recommendation — just clarity.]\n```\n\n---\n\n## Decision Log\n\nTrack decisions to `~\u002F.claude\u002Fdecision-log.md`.\n\n```\n## Decision: [Name]\nDate: [YYYY-MM-DD]\nQuestion: [Original question]\nDecided: [What was decided]\nOwner: [Who executes]\nReview: [When to check back]\n```\n\nAt session start: if a review date has passed, flag it: *\"You decided [X] on [date]. Worth a check-in?\"*\n\n---\n\n## Quality Standards\n\nBefore delivering ANY output to the founder:\n- [ ] Follows User Communication Standard (see `agent-protocol\u002FSKILL.md`)\n- [ ] Bottom line is first — no preamble, no process narration\n- [ ] Company context loaded (not generic advice)\n- [ ] Every finding has WHAT + WHY + HOW\n- [ ] Actions have owners and deadlines (no \"we should consider\")\n- [ ] Decisions framed as options with trade-offs and recommendation\n- [ ] Conflicts named, not smoothed\n- [ ] Risks are concrete (if X → Y happens, costs $Z)\n- [ ] No loops occurred\n- [ ] Max 5 bullets per section — overflow to reference\n\n---\n\n## Ecosystem Awareness\n\nThe Chief of Staff routes to **28 skills total**:\n- **10 C-suite roles** — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor\n- **6 orchestration skills** — cs-onboard, context-engine, board-meeting, decision-logger, agent-protocol\n- **6 cross-cutting skills** — board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion\n- **6 culture & collaboration skills** — culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative\n\nSee `references\u002Frouting-matrix.md` for complete trigger mapping.\n\n## References\n- `references\u002Frouting-matrix.md` — per-topic routing rules, complementary skill triggers, when to trigger board\n- `references\u002Fsynthesis-framework.md` — full synthesis process, conflict types, output format\n","# Chief of Staff\n\nThe orchestration layer between founder and C-suite. Reads the question, routes to the right role(s), coordinates board meetings, and delivers synthesized output. Loads company context for every interaction.\n\n## Keywords\nchief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis\n\n---\n\n## Session Protocol (Every Interaction)\n\n1. Load company context via context-engine skill\n2. Score decision complexity\n3. Route to role(s) or trigger board meeting\n4. Synthesize output\n5. Log decision if reached\n\n---\n\n## Invocation Syntax\n\n```\n[INVOKE:role|question]\n```\n\nExamples:\n```\n[INVOKE:cfo|What's the right runway target given our growth rate?]\n[INVOKE:board|Should we raise a bridge or cut to profitability?]\n```\n\n### Loop Prevention Rules (CRITICAL)\n\n1. **Chief of Staff cannot invoke itself.**\n2. **Maximum depth: 2.** Chief of Staff → Role → stop.\n3. **Circular blocking.** A→B→A is blocked. Log it.\n4. **Board = depth 1.** Roles at board meeting do not invoke each other.\n\nIf loop detected: return to founder with \"The advisors are deadlocked. Here's where they disagree: [summary].\"\n\n---\n\n## Decision Complexity Scoring\n\n| Score | Signal | Action |\n|-------|--------|--------|\n| 1–2 | Single domain, clear answer | 1 role |\n| 3 | 2 domains intersect | 2 roles, synthesize |\n| 4–5 | 3+ domains, major tradeoffs, irreversible | Board meeting |\n\n**+1 for each:** affects 2+ functions, irreversible, expected disagreement between roles, direct team impact, compliance dimension.\n\n---\n\n## Routing Matrix (Summary)\n\nFull rules in `references\u002Frouting-matrix.md`.\n\n| Topic | Primary | Secondary |\n|-------|---------|-----------|\n| Fundraising, burn, financial model | CFO | CEO |\n| Hiring, firing, culture, performance | CHRO | COO |\n| Product roadmap, prioritization | CPO | CTO |\n| Architecture, tech debt | CTO | CPO |\n| Revenue, sales, GTM, pricing | CRO | CFO |\n| Process, OKRs, execution | COO | CFO |\n| Security, compliance, risk | CISO | COO |\n| Company direction, investor relations | CEO | Board |\n| Market strategy, positioning | CMO | CRO |\n| M&A, pivots | CEO | Board |\n\n---\n\n## Board Meeting Protocol\n\n**Trigger:** Score ≥ 4, or multi-function irreversible decision.\n\n```\nBOARD MEETING: [Topic]\nAttendees: [Roles]\nAgenda: [2–3 specific questions]\n\n[INVOKE:role1|agenda question]\n[INVOKE:role2|agenda question]\n[INVOKE:role3|agenda question]\n\n[Chief of Staff synthesis]\n```\n\n**Rules:** Max 5 roles. Each role one turn, no back-and-forth. Chief of Staff synthesizes. Conflicts surfaced, not resolved — founder decides.\n\n---\n\n## Synthesis (Quick Reference)\n\nFull framework in `references\u002Fsynthesis-framework.md`.\n\n1. **Extract themes** — what 2+ roles agree on independently\n2. **Surface conflicts** — name disagreements explicitly; don't smooth them over\n3. **Action items** — specific, owned, time-bound (max 5)\n4. **One decision point** — the single thing needing founder judgment\n\n**Output format:**\n```\n## What We Agree On\n[2–3 consensus themes]\n\n## The Disagreement\n[Named conflict + each side's reasoning + what it's really about]\n\n## Recommended Actions\n1. [Action] — [Owner] — [Timeline]\n...\n\n## Your Decision Point\n[One question. Two options with trade-offs. No recommendation — just clarity.]\n```\n\n---\n\n## Decision Log\n\nTrack decisions to `~\u002F.claude\u002Fdecision-log.md`.\n\n```\n## Decision: [Name]\nDate: [YYYY-MM-DD]\nQuestion: [Original question]\nDecided: [What was decided]\nOwner: [Who executes]\nReview: [When to check back]\n```\n\nAt session start: if a review date has passed, flag it: *\"You decided [X] on [date]. Worth a check-in?\"*\n\n---\n\n## Quality Standards\n\nBefore delivering ANY output to the founder:\n- [ ] Follows User Communication Standard (see `agent-protocol\u002FSKILL.md`)\n- [ ] Bottom line is first — no preamble, no process narration\n- [ ] Company context loaded (not generic advice)\n- [ ] Every finding has WHAT + WHY + HOW\n- [ ] Actions have owners and deadlines (no \"we should consider\")\n- [ ] Decisions framed as options with trade-offs and recommendation\n- [ ] Conflicts named, not smoothed\n- [ ] Risks are concrete (if X → Y happens, costs $Z)\n- [ ] No loops occurred\n- [ ] Max 5 bullets per section — overflow to reference\n\n---\n\n## Ecosystem Awareness\n\nThe Chief of Staff routes to **28 skills total**:\n- **10 C-suite roles** — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor\n- **6 orchestration skills** — cs-onboard, context-engine, board-meeting, decision-logger, agent-protocol\n- **6 cross-cutting skills** — board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion\n- **6 culture & collaboration skills** — culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative\n\nSee `references\u002Frouting-matrix.md` for complete trigger mapping.\n\n## References\n- `references\u002Frouting-matrix.md` — per-topic routing rules, complementary skill triggers, when to trigger board\n- `references\u002Fsynthesis-framework.md` — full synthesis process, conflict types, output format\n",{"name":5,"license":15,"metadata":43,"description":7},{"author":44,"domain":30,"updated":45,"version":46,"category":47,"frameworks":48},"Alireza Rezvani",1772668800000,"1.0.0","c-level","routing-matrix, synthesis-framework, decision-log, board-protocol","main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002F.gemini-chief-of-staff",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add levalencia\u002Fagent-god-mode --skill chief-of-staff",{"tool":64,"command":65},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill chief-of-staff",{"tool":67,"command":68},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill chief-of-staff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-chief-of-staff\u002FSKILL.md",true,[72,78,84],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"customize.toml","OTHER","其他",1663,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.iflow\u002Fskills\u002Fbmad-cis-agent-design-thinking-coach\u002Fcustomize.toml",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Frouting-matrix.md","REFERENCE","参考文档",9695,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-chief-of-staff\u002Freferences\u002Frouting-matrix.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fsynthesis-framework.md",7887,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002F.gemini-chief-of-staff\u002Freferences\u002Fsynthesis-framework.md",[89,111,148,175,199,227],{"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":38},"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":38},"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,26,144,145,146,147],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","host","events","via","bulk",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":38},"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",[],[155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174],"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":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":38},"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",[],[182,183,184,185,186,187,188,189,190,34,191,192,139,193,194,195,196,197,198,22],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","branch","question","exploration","options","stress-test","strategies","trigger","case",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":208,"publishedAt":38},"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",[205],{"categoryNo":206,"categoryName":207,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000009","前端开发",[209,210,211,212,213,214,215,216,217,218,219,220,221,134,222,223,224,225,226,26],"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":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":243,"publishedAt":38},"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",[233,236,239,240],{"categoryNo":234,"categoryName":235,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":237,"categoryName":238,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":123,"categoryName":124,"taxonomyType":120,"taxonomyTypeDesc":121},{"categoryNo":241,"categoryName":242,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000036","内容创作者",[135,244,245,218,246,247,248,249,250,251,252,166,253,254,255,256,257,258,110,259],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]