Loading
/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention i
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add alirezarezvani/claude-skills --skill cco-review -a cursor -y
/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.
/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.
Command: /cs:cco-review <plan>
The 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.
Not NRR. Gross. NRR can hide a leaky bucket behind expansion.
retention_decomposition_analyzer.pyIf you can't name it, you don't understand churn.
Long TTV signals different problems by segment.
If "none" — your segmentation is broken.
customer_segmentation_designer.py to surface kill listWrong model wastes capacity.
cs_coverage_calculator.py to size the teamMisalignment is the leading indicator of CS failure.
# 1. Retention decomposition (always start here)
python ../../../c-level-advisor/skills/chief-customer-officer-advisor/scripts/retention_decomposition_analyzer.py cohorts.json
# 2. Segmentation audit
python ../../../c-level-advisor/skills/chief-customer-officer-advisor/scripts/customer_segmentation_designer.py customers.json
# 3. Coverage sizing (if making CS team changes)
python ../../../c-level-advisor/skills/chief-customer-officer-advisor/scripts/cs_coverage_calculator.py book.json
# CCO Review: <plan>
**Date:** YYYY-MM-DD
## The Decision Being Made
[one sentence — retention | segmentation | coverage | next hire]
## Retention (if applicable)
- GRR: X% (vs vanity NRR of Y%)
- Top churn driver: <category> at X% of churn
- Preventable churn: X% (CS-controllable)
- Leaky-bucket pattern? yes/no
## Segmentation (if applicable)
- Tier distribution: Strategic X / Enterprise X / Mid-market X / SMB X
- Kill list size: N customers (X% of customers, Y% of ARR)
- Upgrade candidates: N
## Coverage (if applicable)
- Current CSMs: N | Required now: M | Required 12mo: P
- Annual cost (12mo): $X
- Manager trigger fired: yes/no
## Org (if applicable)
- Next hire: <CSM | Support | AM | IM | CS Ops | Customer Marketing>
- Why this, not the alternative: <one line>
- Customer outcome unblocked: <specific>
## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK
## Next Steps
[3 concrete actions]
/cs:cpo-review — if churn root cause is product_fit or no_value_realized/cs:cro-review — if expansion math or comp alignment is in question/cs:cfo-review — for CS cost commitments and retention-impact-on-revenuecs-chro-advisor agent — for CS hires, comp, ladder/cs:decide — log the verdict/cs:freeze 30 — on multi-year CS comp plan changescs-cco-advisorchief-customer-officer-advisor../../../business-growth/ (tactical CS execution)Version: 1.0.0