[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754PC0FSM93TJWVKGYQV6YN":3,"skill-same:01M754PC0FSM93TJWVKGYQV6YN":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":13,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M754PC0FSM93TJWVKGYQV6YN","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.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29},"Alireza Rezvani","orchestration",1772668800000,"1.0.0","c-level","routing-matrix, synthesis-framework, decision-log, board-protocol","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fchief-of-staff","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ASoudy\u002FAGS --skill chief-of-staff",{"tool":42,"command":43},"bunx","bunx skills add ASoudy\u002FAGS --skill chief-of-staff",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill chief-of-staff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Frouting-matrix.md","REFERENCE","参考文档",9695,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fchief-of-staff\u002Freferences\u002Frouting-matrix.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fsynthesis-framework.md",7887,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fchief-of-staff\u002Freferences\u002Fsynthesis-framework.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]