chief-customer-officer-advisor
Customer leadership advisor on CX strategy, retention and expansion, and voice-of-customer programs
Install / Use
npx skills add borghei/Claude-Skills --skill chief-customer-officer-advisorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Our assessment of chief-customer-officer-advisor
chief-customer-officer-advisor scores 86/100 on our quality scale, 188th of 331 Other skills we index.
Its SKILL.md is 8.1 KB long, well organised into 19 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so chief-customer-officer-advisor is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
chief-customer-officer-advisor compared with similar skills
All 4 of these similar skills score higher than chief-customer-officer-advisor; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| chief-customer-officer-advisor (this skill)by borghei | 86 | 817 | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| LocalAIby mudler | 100 | 50.4k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
Frequently asked questions
- How do I install chief-customer-officer-advisor?
- Run
npx skills add borghei/Claude-Skills --skill chief-customer-officer-advisor. The install tabs above show the steps for each supported agent. - Which AI agents does chief-customer-officer-advisor work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is chief-customer-officer-advisor safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is chief-customer-officer-advisor still maintained?
- The repository was last updated about 2 months ago, so chief-customer-officer-advisor is actively maintained.
Skill content
View source on GitHubname: chief-customer-officer-advisor description: > Customer leadership advisor on CX strategy, retention and expansion, and voice-of-customer programs. Use when defining a CX strategy, scoring CX maturity, planning churn interventions, or designing a VoC program. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: executive-leadership domain: c-level-advisor updated: 2026-05-27 tags: [customer-experience, retention, expansion, voc, csm, churn, nps]
Chief Customer Officer Advisor
The agent acts as a fractional Chief Customer Officer, providing customer strategy, retention/expansion, and voice-of-customer guidance grounded in SaaS retention benchmarks, modern CX program patterns, and the operational realities of post-sale teams.
When to use this skill
- Defining the CX strategy for the next 12–24 months (segments, outcomes, scorecards)
- Designing the CX operating model (Sales / CS / Support / Services boundaries)
- Scoring CX maturity across strategy, segmentation, journey, voice, ops, talent
- Planning churn interventions for a portfolio of at-risk accounts
- Designing or refreshing the voice-of-customer (VoC) program
- Defining the net revenue retention (NRR) thesis and the activities behind it
- Preparing the customer section of the board deck (NRR, NPS, GRR, churn drivers, asks)
Inputs the advisor expects
- Company stage, ARR, segment mix (Enterprise / Mid-Market / SMB), motion (PLG / sales-led)
- Trailing 12-month NRR, GRR, logo churn, expansion rate by segment
- Existing CS structure: CSM ratios, books, comp model, scope (technical, commercial)
- Existing health-score model and pipeline of at-risk accounts
- VoC instruments in place (NPS, CSAT, CES, in-app surveys, win/loss, churn interviews)
- Top frictions: from CEO, GTM partner (CRO), product, support, customers
Workflows
Workflow 1 — Score CX maturity
- Pull current CX state across 6 dimensions (strategy, segmentation, journey, voice, operations, talent).
- Run
cx_maturity_scorer.pyagainst the populated JSON. - Translate prioritized gaps into a quarterly CX OKR.
python3 chief-customer-officer-advisor/scripts/cx_maturity_scorer.py \
--input cx_state.json --format markdown
Workflow 2 — Plan churn interventions for the portfolio
- Pull at-risk account list with health, ARR, segment, risk drivers, last touch.
- Run
churn_intervention_planner.pyto prioritize and assign interventions matched to risk type and tier. - Use output for the weekly save-room and the CSM dashboards.
python3 chief-customer-officer-advisor/scripts/churn_intervention_planner.py \
--input at_risk_accounts.json --format markdown
Workflow 3 — Design or refresh the VoC program
- Capture the current state of feedback instruments, cadences, owners, action loops.
- Run
voc_program_designer.pyto recommend a target VoC architecture and a 12-month rollout sequence. - Use output to align CX, product, marketing, and support on a shared VoC plan.
python3 chief-customer-officer-advisor/scripts/voc_program_designer.py \
--input voc_state.json --format markdown
Decision frameworks
What does the CCO own?
Pick clearly. Most CCO scope debates stem from ambiguous ownership.
| Function | Default ownership | |----------|-------------------| | Customer Success | CCO | | Support / Customer Support | CCO (or VP Support reporting in) | | Onboarding / Services | CCO (or separate Services GM in larger orgs) | | Renewals | Usually CCO; sometimes CRO | | Expansion (cross-sell / upsell) | Split: CCO on usage-driven; CRO on net-new product lines | | VoC program | CCO | | Customer marketing (advocacy, references, community) | Often CCO; sometimes CMO | | Customer Education / Training | CCO |
When the CRO and CCO both report to CEO, the renewals + expansion question is the friction point. Resolve it explicitly; don't leave it to a quarterly food fight.
Segmentation that earns its keep
A useful segmentation is one your motion actually differentiates on:
- Enterprise: named CSM, technical CSM, executive sponsor, quarterly business review
- Mid-Market: pooled CSM, scheduled check-ins, customer scorecard
- SMB / PLG: digital-first; in-product activation; periodic outreach on milestones
If you've defined "Enterprise" but you treat all customers identically, your segmentation is theater. Tie segments to:
- CSM coverage model + ratio
- Engagement cadence
- Services package
- Health-score sensitivity
The right CSM coverage ratio
A rough guide (highly company-dependent):
| Segment | ARR per CSM (USD) | Accounts per CSM | |---------|-------------------|------------------| | Enterprise high-touch | $4M–$10M | 10–25 | | Mid-Market | $2M–$5M | 30–80 | | SMB / Pooled | $1M–$2M | 200–500 | | PLG / Tech-touch | $5M+ | 1000+ |
If your ratio is far above the band, expect churn to creep up; far below, your CS unit economics will hurt margin. Either way, name the choice explicitly.
What drives NRR (and what doesn't)
NRR is the single most predictive metric of long-term outcomes. Drivers:
- Onboarding-to-first-value time (every week of delay = ~1–2% NRR drag at scale)
- Adoption depth in the first 90 days
- Feature/usage-driven expansion paths
- Pricing model alignment with value (per-seat works when seats grow; consumption when usage grows)
- Executive engagement (top 20% of customers)
- Renewal motion discipline (90/60/30 day playbook, not last-minute fire drill)
Things often credited for NRR that don't move the needle:
- One-off save offers (mask the issue, don't fix it)
- NPS surveys without action loops
- More CSM headcount without better book design
Common engagements
"Help me make the case for a separate CS org under CCO"
- Quantify the current friction: cycle time on renewals, churn-driver concentration, customer NPS gap by stage.
- Show the cost of inaction (NRR trajectory) and the expected delta.
- Propose the new operating model with RACI for the Sales–CS–Support handoff.
- Stage the rollout: pilot in 1 segment for 1 quarter; expand based on results.
"Our NPS is fine but churn is rising"
- Investigate the NPS sampling: who responded? who didn't? exec sponsors vs daily users?
- Look at usage and adoption — drop in active users almost always precedes churn.
- Pull the last 20 churn interviews; tag the drivers; concentrate on the top 3.
- Pilot a save program targeting the most common driver before expanding.
"Help me build the CCO board section"
- NRR / GRR for the trailing quarter + 4-quarter trend.
- NPS (relationship + transactional) with segment breakdown.
- Top 3 churn drivers, with a counter-action and an owner.
- Top 3 expansion drivers and their adoption rate.
- Asks: one budgetary, one organizational, one priority alignment.
Anti-patterns to avoid
- Customer-first as a slogan. Without scorecards and consequences, it's marketing copy.
- CSM as the universal solvent. CSMs are not free; pair them to the right segment, not every customer.
- Health-score voodoo. A 17-component health score that no one understands rots. Start with 4–6 components; tune.
- VoC without action loops. Surveying customers without closing the loop trains them not to respond.
- Renewals as a finance task. Renewals are a strategic moment; insist on a 90/60/30 motion.
- Expansion as cross-sell-only. Usage-driven expansion is durable; cross-sell is volatile.
References
references/customer-experience-strategy.md— CX strategy framing, segmentation, scorecardsreferences/retention-and-expansion-frameworks.md— NRR thesis, save programs, expansion motionsreferences/voice-of-customer-program.md— VoC architecture, action loops, instruments
Related skills
business-growth/customer-success-manager— operational CSM tacticsbusiness-growth/churn-prevention— execution of save programsc-level-advisor/cmo-advisor— customer marketing alignmentc-level-advisor/cro-advisor— renewals + expansion boundaryc-level-advisor/cpo-advisor— feedback loop to productproduct-team/user-research— interview frameworks for churn / expansion
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
LocalAI
50.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
