[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CJV0PCR8ECMVGV0RF5QB7":3,"skill-same:01M75CJV0PCR8ECMVGV0RF5QB7":54},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M75CJV0PCR8ECMVGV0RF5QB7","coo-advisor",null,"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.","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\u002Fcoo-advisor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"coo-advisor\"\ndescription: \"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: coo-leadership\n  updated: 2026-03-05\n  python-tools: ops_efficiency_analyzer.py, okr_tracker.py\n  frameworks: scaling-playbook, ops-cadence, process-frameworks\n---\n\n# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n","# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","coo-leadership",1772668800000,"1.0.0","c-level","scaling-playbook, ops-cadence, process-frameworks","ops_efficiency_analyzer.py, okr_tracker.py","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcoo-advisor",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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add agisota\u002Fold-one --skill coo-advisor",{"tool":46,"command":47},"bunx","bunx skills add agisota\u002Fold-one --skill coo-advisor",{"tool":49,"command":50},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill coo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcoo-advisor\u002FSKILL.md",true,[],[55,62,69,78,85,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]