[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C2MM7P87AHQBQQMPPX4XG":3,"skill-same:01M75C2MM7P87AHQBQQMPPX4XG":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75C2MM7P87AHQBQQMPPX4XG","cco-review",null,"\u002Fcs:cco-review \u003Cplan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring.","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\u002Fcco-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"cco-review\"\ndescription: \"\u002Fcs:cco-review \u003Cplan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring.\"\n---\n\n# \u002Fcs:cco-review — CCO Forcing Questions\n\n**Command:** `\u002Fcs:cco-review \u003Cplan>`\n\nThe retention-obsessed CCO pressure-tests any plan that touches customer experience. Six questions before any retention claim, segmentation change, CS team expansion, or major CS hire.\n\n## When to Run\n\n- Before any board narrative that includes a retention number\n- Before approving a CS team headcount expansion\n- Before re-segmenting the customer base or changing tier definitions\n- Before launching a customer marketing or advocacy program\n- Before a major CS hire (CSM, AM, Implementation, Customer Marketing)\n- When NRR is \"great\" but churn complaints from CSMs are increasing\n- Before deciding whether to add an AM role separate from CSM\n\n## The Six CCO Questions\n\n### 1. What's the GROSS retention rate?\n**Not NRR. Gross.** NRR can hide a leaky bucket behind expansion.\n- GRR healthy ≥ 90% at growth stage, ≥ 95% at scale\n- If GRR \u003C 85% but NRR > 100%, the product is failing for 15%+ of customers; expansion is masking the failure\n- Run `retention_decomposition_analyzer.py`\n\n### 2. What's the #1 reason customers leave?\n**If you can't name it, you don't understand churn.**\n- 7-category taxonomy: product_fit \u002F competitor_loss \u002F no_value_realized \u002F pricing \u002F champion_left \u002F company_event \u002F tactical_failure\n- Preventable churn = product_fit + no_value_realized + tactical_failure\n- If preventable > 50%, CS has clear leverage; if \u003C 30%, churn is structural (ICP, market, competition)\n\n### 3. What's the median time-to-value (TTV) by segment?\n**Long TTV signals different problems by segment.**\n- Long TTV in low tier = ICP misfit; downgrade or kill\n- Long TTV in high tier = onboarding broken; fix the Implementation Manager handoff\n- TTV is a leading indicator of GRR\n\n### 4. Which customer would you fire today?\n**If \"none\" — your segmentation is broken.**\n- Some accounts cost more than they earn (support cost > 50% of ARR + low ICP fit)\n- Run `customer_segmentation_designer.py` to surface kill list\n- The 3 paths for kill candidates: non-renewal \u002F downgrade-to-tech-touch \u002F raise-price-to-cost-recover\n\n### 5. What's the ARR-per-CSM ratio, and is the model pooled or named?\n**Wrong model wastes capacity.**\n- Strategic: named + exec sponsor, $300K-$1M ARR\u002FCSM\n- Enterprise: named, $500K-$2M\n- Mid-market: pooled, $2M-$5M\n- SMB: tech-touch, $5M+\n- Run `cs_coverage_calculator.py` to size the team\n\n### 6. Is CS in your comp plan, and how is it different from Sales comp?\n**Misalignment is the leading indicator of CS failure.**\n- CS comp: 70\u002F30 base\u002Fvariable typical\n- Variable: 50% gross retention + 30% net retention + 20% activity\n- Anti-pattern: comp CSMs on NPS — they game it\n- Anti-pattern: comp CSMs same as Sales — they sell instead of serve\n\n## Workflow\n\n```bash\n# 1. Retention decomposition (always start here)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fretention_decomposition_analyzer.py cohorts.json\n\n# 2. Segmentation audit\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcustomer_segmentation_designer.py customers.json\n\n# 3. Coverage sizing (if making CS team changes)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcs_coverage_calculator.py book.json\n```\n\n## Output Format\n\n```markdown\n# CCO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — retention | segmentation | coverage | next hire]\n\n## Retention (if applicable)\n- GRR: X% (vs vanity NRR of Y%)\n- Top churn driver: \u003Ccategory> at X% of churn\n- Preventable churn: X% (CS-controllable)\n- Leaky-bucket pattern? yes\u002Fno\n\n## Segmentation (if applicable)\n- Tier distribution: Strategic X \u002F Enterprise X \u002F Mid-market X \u002F SMB X\n- Kill list size: N customers (X% of customers, Y% of ARR)\n- Upgrade candidates: N\n\n## Coverage (if applicable)\n- Current CSMs: N | Required now: M | Required 12mo: P\n- Annual cost (12mo): $X\n- Manager trigger fired: yes\u002Fno\n\n## Org (if applicable)\n- Next hire: \u003CCSM | Support | AM | IM | CS Ops | Customer Marketing>\n- Why this, not the alternative: \u003Cone line>\n- Customer outcome unblocked: \u003Cspecific>\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:cpo-review` — if churn root cause is product_fit or no_value_realized\n- `\u002Fcs:cro-review` — if expansion math or comp alignment is in question\n- `\u002Fcs:cfo-review` — for CS cost commitments and retention-impact-on-revenue\n- `\u002Fcs:chro-review` — for CS hires, comp, ladder\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 30` — on multi-year CS comp plan changes\n\n## Related\n\n- Agent: [`cs-cco-advisor`](..\u002F..\u002Fagents\u002Fcs-cco-advisor.md)\n- Skill: [`chief-customer-officer-advisor`](..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002F..\u002Fbusiness-growth\u002F` (tactical CS execution)\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:cco-review — CCO Forcing Questions\n\n**Command:** `\u002Fcs:cco-review \u003Cplan>`\n\nThe retention-obsessed CCO pressure-tests any plan that touches customer experience. Six questions before any retention claim, segmentation change, CS team expansion, or major CS hire.\n\n## When to Run\n\n- Before any board narrative that includes a retention number\n- Before approving a CS team headcount expansion\n- Before re-segmenting the customer base or changing tier definitions\n- Before launching a customer marketing or advocacy program\n- Before a major CS hire (CSM, AM, Implementation, Customer Marketing)\n- When NRR is \"great\" but churn complaints from CSMs are increasing\n- Before deciding whether to add an AM role separate from CSM\n\n## The Six CCO Questions\n\n### 1. What's the GROSS retention rate?\n**Not NRR. Gross.** NRR can hide a leaky bucket behind expansion.\n- GRR healthy ≥ 90% at growth stage, ≥ 95% at scale\n- If GRR \u003C 85% but NRR > 100%, the product is failing for 15%+ of customers; expansion is masking the failure\n- Run `retention_decomposition_analyzer.py`\n\n### 2. What's the #1 reason customers leave?\n**If you can't name it, you don't understand churn.**\n- 7-category taxonomy: product_fit \u002F competitor_loss \u002F no_value_realized \u002F pricing \u002F champion_left \u002F company_event \u002F tactical_failure\n- Preventable churn = product_fit + no_value_realized + tactical_failure\n- If preventable > 50%, CS has clear leverage; if \u003C 30%, churn is structural (ICP, market, competition)\n\n### 3. What's the median time-to-value (TTV) by segment?\n**Long TTV signals different problems by segment.**\n- Long TTV in low tier = ICP misfit; downgrade or kill\n- Long TTV in high tier = onboarding broken; fix the Implementation Manager handoff\n- TTV is a leading indicator of GRR\n\n### 4. Which customer would you fire today?\n**If \"none\" — your segmentation is broken.**\n- Some accounts cost more than they earn (support cost > 50% of ARR + low ICP fit)\n- Run `customer_segmentation_designer.py` to surface kill list\n- The 3 paths for kill candidates: non-renewal \u002F downgrade-to-tech-touch \u002F raise-price-to-cost-recover\n\n### 5. What's the ARR-per-CSM ratio, and is the model pooled or named?\n**Wrong model wastes capacity.**\n- Strategic: named + exec sponsor, $300K-$1M ARR\u002FCSM\n- Enterprise: named, $500K-$2M\n- Mid-market: pooled, $2M-$5M\n- SMB: tech-touch, $5M+\n- Run `cs_coverage_calculator.py` to size the team\n\n### 6. Is CS in your comp plan, and how is it different from Sales comp?\n**Misalignment is the leading indicator of CS failure.**\n- CS comp: 70\u002F30 base\u002Fvariable typical\n- Variable: 50% gross retention + 30% net retention + 20% activity\n- Anti-pattern: comp CSMs on NPS — they game it\n- Anti-pattern: comp CSMs same as Sales — they sell instead of serve\n\n## Workflow\n\n```bash\n# 1. Retention decomposition (always start here)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fretention_decomposition_analyzer.py cohorts.json\n\n# 2. Segmentation audit\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcustomer_segmentation_designer.py customers.json\n\n# 3. Coverage sizing (if making CS team changes)\npython ..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002Fscripts\u002Fcs_coverage_calculator.py book.json\n```\n\n## Output Format\n\n```markdown\n# CCO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## The Decision Being Made\n[one sentence — retention | segmentation | coverage | next hire]\n\n## Retention (if applicable)\n- GRR: X% (vs vanity NRR of Y%)\n- Top churn driver: \u003Ccategory> at X% of churn\n- Preventable churn: X% (CS-controllable)\n- Leaky-bucket pattern? yes\u002Fno\n\n## Segmentation (if applicable)\n- Tier distribution: Strategic X \u002F Enterprise X \u002F Mid-market X \u002F SMB X\n- Kill list size: N customers (X% of customers, Y% of ARR)\n- Upgrade candidates: N\n\n## Coverage (if applicable)\n- Current CSMs: N | Required now: M | Required 12mo: P\n- Annual cost (12mo): $X\n- Manager trigger fired: yes\u002Fno\n\n## Org (if applicable)\n- Next hire: \u003CCSM | Support | AM | IM | CS Ops | Customer Marketing>\n- Why this, not the alternative: \u003Cone line>\n- Customer outcome unblocked: \u003Cspecific>\n\n## Verdict\n🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:cpo-review` — if churn root cause is product_fit or no_value_realized\n- `\u002Fcs:cro-review` — if expansion math or comp alignment is in question\n- `\u002Fcs:cfo-review` — for CS cost commitments and retention-impact-on-revenue\n- `\u002Fcs:chro-review` — for CS hires, comp, ladder\n- `\u002Fcs:decide` — log the verdict\n- `\u002Fcs:freeze 30` — on multi-year CS comp plan changes\n\n## Related\n\n- Agent: [`cs-cco-advisor`](..\u002F..\u002Fagents\u002Fcs-cco-advisor.md)\n- Skill: [`chief-customer-officer-advisor`](..\u002F..\u002F..\u002Fskills\u002Fchief-customer-officer-advisor\u002FSKILL.md)\n- Adjacent: `..\u002F..\u002F..\u002F..\u002Fbusiness-growth\u002F` (tactical CS execution)\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcco-review",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill cco-review",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill cco-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill cco-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcco-review\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":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},"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":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},"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":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},"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",[],[]]