[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C51TKTA1JSSVGJM3EAC1G":3,"skill-same:01M75C51TKTA1JSSVGJM3EAC1G":53},{"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":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M75C51TKTA1JSSVGJM3EAC1G","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\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","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fchief-of-staff",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add agisota\u002Fold-one --skill chief-of-staff",{"tool":45,"command":46},"bunx","bunx skills add agisota\u002Fold-one --skill chief-of-staff",{"tool":48,"command":49},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill chief-of-staff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fchief-of-staff\u002FSKILL.md",true,[],[54,61,68,77,84,91],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"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},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\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":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","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\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]