agent-launcher-orchest…
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use for retention strategy, customer segmentation or CS team sizing decisions (GRR vs NRR, churn causes, pooled vs named CSMs). Runs retention_decomposition_analyzer.py, customer_segmentation_designer.py and cs_coverage_calculator.py.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor -a windsurf -y
name: "chief-customer-officer-advisor" description: "Use for retention strategy, customer segmentation or CS team sizing decisions (GRR vs NRR, churn causes, pooled vs named CSMs). Runs retention_decomposition_analyzer.py, customer_segmentation_designer.py and cs_coverage_calculator.py." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: chief-customer-officer-leadership updated: 2026-05-13 python-tools: retention_decomposition_analyzer.py, customer_segmentation_designer.py, cs_coverage_calculator.py frameworks: retention-decomposition, customer-segmentation, cs-coverage-model, cs-team-org
Strategic customer leadership for startup CCOs and founders without one. **Four decisions, no generic CS survey:**
1. **What's our retention architecture — and is gross retention vs NRR honest?** — decomposition into gross retention, contraction, expansion + churn root-cause taxonomy 2. **How do we segment customers for differential investment?** — tier design + ICP fit scoring + investment-per-segment math 3. **What's the CS team's coverage model — and when do we go pooled vs named?** — coverage ratio calculator + transition thresholds 4. **What CS role do we hire next?** — stage-to-role map (CS ≠ Support ≠ AM ≠ Implementation)
This skill does **not** cover tactical CS implementation. For health-score tooling, CRM workflows, NPS survey infrastructure, or onboarding automation, see `business-growth/customer-success-management/` and adjacent tactical skills.
CCO, chief customer officer, customer success, retention strategy, gross retention, net retention, NRR, GRR, logo retention, dollar retention, churn, contraction, expansion, downsell, customer lifetime value, CLV, LTV, time-to-value, TTV, time-to-first-value, customer health score, NPS, CSAT, customer effort score, segmentation, ICP fit, tier design, low-touch, high-touch, tech-touch, pooled CSM, named CSM, customer success manager, account manager, AM, implementation manager, IM, customer success operations, CS ops, book of business, ratio, ARR-per-CSM, customer marketing, advocacy, expansion playbook, voice of customer, VoC
# Decision A: Decompose retention honestly python scripts/retention_decomposition_analyzer.py # embedded B2B SaaS sample python scripts/retention_decomposition_analyzer.py path/to/cohorts.json # Decision B: Design customer segmentation + differential investment python scripts/customer_segmentation_designer.py # embedded 4-tier sample python scripts/customer_segmentation_designer.py path/to/customers.json # Decision C: Calculate CS team coverage model python scripts/cs_coverage_calculator.py # embedded 350-customer sample python scripts/cs_coverage_calculator.py path/to/book.json
**The trap:** "Our NRR is 115%, retention is great."
The truth: NRR = Gross Retention − Contraction + Expansion. A 115% NRR with 85% gross retention is a leaky bucket masked by upsells. A 115% NRR with 98% gross retention is a healthy product.
**Mandatory decomposition every quarter:**
| Metric | What it measures | Health threshold (B2B SaaS) | |---|---|---| | **Gross Retention (GRR)** | $ from existing customers minus churn + contraction | ≥ 90% at growth stage; ≥ 95% at scale | | **Logo Retention** | % of customers who renewed | ≥ 85% at growth; ≥ 90% at scale | | **Net Revenue Retention (NRR)** | GRR + expansion | ≥ 110% at growth; ≥ 120% at scale | | **Contraction** | $ from existing customers reducing seats/usage | < 5% annually | | **Expansion** | $ from existing customers growing | 15-25% annually at healthy |
**Run** `retention_decomposition_analyzer.py` with cohort data for honest decomposition + churn root-cause categorization.
See `references/retention_decomposition.md` for the 7-category churn taxonomy + leading indicator playbook.
**The trap:** "Every customer is important."
The reality: customers exist on a spectrum of ICP fit × strategic value. Treating them identically wastes CS capacity and ignores expansion opportunity.
**4-tier framework (B2B SaaS baseline):**
| Tier | ARR range | Coverage | Investment per account/yr | |---|---|---|---| | **Strategic** | Top 5%, often $100K+ | Named CSM + executive sponsor | $20K-50K | | **Enterprise** | Next 15-20%, $20K-100K | Named CSM | $5K-15K | | **Mid-market** | Next 30-40%, $5K-20K | Pooled CSM + automation | $1K-3K | | **SMB / Long-tail** | Bottom 40-50%, <$5K | Tech-touch + self-serve | $50-500 |
**Run** `customer_segmentation_designer.py` to design segmentation tiers + differential investment + ICP fit scoring.
See `references/customer_segmentation_strategy.md` for ICP fit framework, tier transition triggers, and the kill list (customers below the investment floor).
**The trap:** "Hire one CSM per X customers" with a single ratio across all segments.
The reality: coverage model depends on segment, ACV, and complexity. Pooled CSM works for low-touch; named CSM is required for strategic account
415 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when a launched managed agent needs grading against a rubric and improving ('grade my agent', 'is it good enough'). Builds…
Use when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and…
Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates…
Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads…
Use when closing out a launched managed agent ('wrap up', 'what do I own now'). Inventories primitives with…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…