Skip to content

Guide · Agent skill

How to use the CCO Customer Retention Review agent skill (cco-review)

Updated · written with AI from the project's own documentation and checked against our catalogue data

The cco-review skill is a set of instructions that makes Claude act like a retention-focused Chief Customer Officer when you ask it to review a plan. It is aimed at founders and operators who are deciding on customer success headcount, re-segmenting customers, or reading a retention number before a board update. After this guide you will know what the skill does, how to install it from the ZIP, how to trigger it, and what it needs to run its optional scripts.

CCO Customer Retention Reviewalirezarezvani/claude-skills · MIT

Quick start

  1. 1Download the ZIP. Download the cco-review skill ZIP from the page and unzip it.
  2. 2Place the skill folder. Move the folder into ~/.claude/skills/ for personal use or .claude/skills/ inside a project.
  3. 3Install the c-level-agents plugin. Make sure Claude Code has the c-level-agents plugin, since the script paths depend on ${CLAUDE_PLUGIN_ROOT}.
  4. 4Describe your plan. Ask for a review in plain language or use /c-level-agents:cco-review followed by the plan.
  5. 5Provide data if you have it. Add cohorts.json, customers.json or book.json to run the helper scripts with Python.
  6. 6Read the verdict. Check the ship, sharpen or block verdict and the three next steps before acting.

What is an agent skill and what does cco-review make the agent do?

An agent skill is a folder containing a SKILL.md file that tells an agent how to handle a specific kind of task. When the skill is active, the agent follows its instructions rather than answering generically. The cco-review skill is built around a command, /c-level-agents:cco-review [plan], that pressure-tests any plan touching customer retention, segmentation, customer success team size, or customer success hiring.

The agent asks six questions about the plan. They cover gross retention (not just net retention), the top reason customers leave, median time-to-value by segment, which customer you would fire today, ARR per CSM and whether the model is pooled or named, and whether customer success compensation is aligned with retention. It then produces a structured verdict of ship, sharpen, or block, with next steps.

Install the cco-review skill from the ZIP

Download the ZIP for the skill from the page you are reading. Unzip it, then place the resulting skill folder in one of two locations: your user skills folder at ~/.claude/skills/ so it is available in every project, or a project-specific .claude/skills/ folder so it applies only to that project.

If you use the Claude apps instead of Claude Code, you can upload the skill under Settings → Capabilities → Skills.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside your project folder
  • Claude apps: Settings → Capabilities → Skills, then upload

Know the plugin requirement before you run it

The skill's command paths reference ${CLAUDE_PLUGIN_ROOT}, so it needs Claude Code with the c-level-agents plugin installed. The skill's own description and workflow use the /c-level-agents:cco-review command, which depends on that plugin. If you only unzip the skill without the plugin, the helper script paths will not resolve.

Trigger the review with a natural request

You can run the review with the command, or describe what you want in plain language. The skill's own guidance says to use it before any board narrative that includes a retention number, before approving CS team headcount expansion, before re-segmenting the customer base, and when net retention looks good but CSM churn complaints are rising.

Describe the plan itself in your request so the agent has something concrete to review. Include the decision you are about to make, the numbers you have, and the segments involved.

  • Using the command: /c-level-agents:cco-review hiring two more CSMs for the mid-market book
  • Natural request: Review my plan to add two CSMs. Gross retention is 84% and NRR is 108%.
  • Natural request: Before I tell the board our retention is strong, pressure-test that number.
  • Natural request: Which customer segments should we keep or stop serving? Run the CCO review.

Run the optional helper scripts on your data

The skill points to three Python scripts that analyse customer data files if you provide them. The workflow starts with retention decomposition on cohorts.json, then a segmentation audit on customers.json, then coverage sizing on book.json when you are changing the CS team. You need Python installed to run them.

The scripts are optional. Without data files the agent can still work through the six questions using the figures you give it.

  • retention_decomposition_analyzer.py takes cohorts.json
  • customer_segmentation_designer.py takes customers.json
  • cs_coverage_calculator.py takes book.json
python ${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/chief-customer-officer-advisor/scripts/retention_decomposition_analyzer.py cohorts.json

Read the output and decide what to do next

The review produces a structured report with sections for the decision being made, retention, segmentation, coverage, org, a verdict shown as 🟢 SHIP, 🟡 SHARPEN, or 🔴 BLOCK, and three concrete next steps. Sections that do not apply to your plan are marked as skipped.

Treat the verdict as a prompt for discussion. The benchmarks and thresholds in the skill are opinionated, and the script outputs are not checked against any independent source.

  • Retention: GRR compared with vanity NRR, top churn driver, preventable churn share
  • Segmentation: tier distribution and kill list size
  • Coverage: current and required CSMs, annual cost, manager trigger
  • Verdict and next steps

Safety notes: scripts and network access

The skill runs scripts, so read them before running them on sensitive data. The skill itself does not use the network. Your customer data files stay on your machine unless you send them elsewhere, so keep real customer records out of shared folders and review the script code if your data is confidential.

  • Runs scripts: yes. Review the Python files before running them on real data.
  • Uses network: no.
  • Use anonymised or sample data if you are unsure.

What people use it for

  • Deciding whether to approve two new CSM roles before the next budget cycle.
  • Checking a board retention figure when net retention looks strong but gross retention may be weak.
  • Re-segmenting the customer base and listing which accounts might be non-renewed, downgraded or repriced.
  • Choosing between a CSM and an Account Manager as the next customer success hire.

Frequently asked questions

How do I install the cco-review skill?

Download the ZIP from the page, unzip it, and place the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.

Is cco-review free to use?

The skill is published under the MIT licence, as stated on the listing. Check the licence file in the source repository for the full terms.

What do I need to run cco-review?

You need Claude Code with the c-level-agents plugin installed, because the command paths reference ${CLAUDE_PLUGIN_ROOT}. Python is needed only if you want to run the optional helper scripts on customer data files.

Does cco-review send my customer data anywhere?

The skill is listed as not using the network. It does run Python scripts on any data files you provide, so review those scripts before using confidential records.

Can I trust the verdict for a board report?

Treat it as a prompt for discussion, not a verified analysis. The listing notes that the benchmarks and thresholds are opinionated and the script outputs are not checked, so verify key figures yourself before presenting them.

What are alternatives to cco-review for retention analysis?

The skill points to related advisors in the same toolkit, such as the cpo-review for product-driven churn, the cro-review for expansion and comp, and the cfo-review for cost and revenue impact. For a non-AI approach, a spreadsheet of gross and net retention by cohort is a common alternative.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use cco-review if you are a founder or operator approving customer success headcount, reviewing a retention number, or deciding which segments to keep, and you want a structured set of hard questions. Pick something else if you need a verified financial or retention analysis, or if your business is outside SaaS-style customer success planning, since the skill's benchmarks are opinionated.

Download the skill

Find exactly what
you're looking for