CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chief-customer-officer-advisor

Chief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS vs Support vs AM distinctions). Use when designing retention strategy, segmenting customers for differential investment, sizing CS team, or sequencing CS hires. Strategic only — does not duplicate engineering/business-growth tactical skills.

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured advisory skill: executable commands with embedded samples, four clearly sequenced workflows with cross-skill checkpoints, and exemplary progressive disclosure verified against real bundle files. The main inefficiency is a keyword-stuffed section and duplicate reference descriptions that pad the token budget without adding action guidance.

Suggestions

Trim the ~60-term Keywords section to the handful of terms not already covered by the description's trigger clause (e.g., 'pooled CSM', 'book of business'), or drop it entirely — it duplicates discovery work the description already does.

Collapse the bottom References section into the inline 'See references/...' notes (or vice versa) so each reference is described once instead of twice with near-identical text.

Add an explicit input-validation step to the workflows (e.g., 'confirm cohort data covers 8 quarters before decomposing') to upgrade implicit checkpoints to explicit ones.

DimensionReasoningScore

Conciseness

Mostly efficient — the tables carry genuinely non-obvious domain data (GRR ≥ 90%/95% thresholds, ARR-per-CSM ratio bands, role ownership distinctions) that Claude does not already know. But it could be tightened: the ~60-term Keywords paragraph ('CCO, chief customer officer, customer success, retention strategy, gross retention...') is trigger stuffing that largely duplicates the description, and each reference is described twice (inline 'See references/...' notes plus a bottom References section with near-identical descriptions).

3 / 5

Actionability

Quick Start gives copy-paste commands that run with embedded sample data ('python scripts/retention_decomposition_analyzer.py # embedded B2B SaaS sample'), all three scripts exist in the bundle, and each of the four workflows specifies concrete inputs, steps, and outputs ('Build customers.json with ARR, tenure, ICP fit signals' → 'Output: new tier assignment + investment-per-tier + kill list'). The Output Standards template makes the deliverable format unambiguous.

5 / 5

Workflow Clarity

Four workflows with clear numbered sequences, stated goals, and cross-check checkpoints ('Cross-check with cs-cro-advisor: does the expansion math add up?', 'Cross-check with cs-chro-advisor on comp + leveling') that serve as review gates. These are advisory analysis workflows, so the destructive/batch validation cap does not apply, but explicit input-data validation (e.g., verifying cohort coverage or data completeness before decomposing) is only implicit — anchor 4's 'minor validation gaps' rather than anchor 5's explicit validation steps.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all four referenced files exist (references/retention_decomposition.md, customer_segmentation_strategy.md, cs_coverage_model.md, cs_team_org_evolution.md) and all three scripts exist. The body keeps decision-level tables inline and pushes depth (7-category churn taxonomy, ramp curves, stage-to-role maps) to clearly signaled one-level-deep references, with each section naming what the reference contains. No nested content references within the bundle.

5 / 5

Total

17

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly answers what (four concrete advisory capabilities with mechanics) and when (four explicit trigger activities), with an explicit scope boundary against tactical skills. The only gaps are a few missing natural synonyms (customer success, CSM, renewals) and unaddressed overlap with adjacent c-level advisor skills on retention/NRR triggers.

DimensionReasoningScore

Specificity

The description enumerates four concrete capability areas each with sub-mechanics: 'retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy)', 'customer segmentation strategy (differential investment across tiers + ICP fit scoring)', 'CS team coverage model (pooled vs named CSM thresholds + ratio math)', and 'CS team org evolution (CS vs Support vs AM distinctions)'. This is comprehensive, multi-action coverage that matches the anchor-5 example; it clearly exceeds the 'minor gaps' of anchor 4 since every named decision area carries concrete mechanics.

5 / 5

Completeness

Both what and when are explicit. The 'what' is the four enumerated capability areas; the 'when' is the concrete trigger clause 'Use when designing retention strategy, segmenting customers for differential investment, sizing CS team, or sequencing CS hires.' This mirrors the anchor-5 exemplar structure exactly; anchor 4's 'when could be more explicit' does not apply since the when-clause lists four specific triggering activities.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'retention strategy', 'gross retention', 'NRR', 'churn', 'ICP fit', 'sizing CS team', 'sequencing CS hires', 'pooled vs named CSM' are phrases a user would naturally say. It falls short of anchor 5 because common variations are missing: 'customer success', 'CSM', 'renewals', 'customer success manager' — terms the body's own Keywords section recognizes but the description omits.

4 / 5

Distinctiveness Conflict Risk

A clear CCO niche with an explicit boundary clause ('Strategic only — does not duplicate engineering/business-growth tactical skills') and distinct triggers like 'sizing CS team' and 'sequencing CS hires'. It sits at anchor 4 rather than 5 because 'retention strategy' and 'NRR' triggers overlap with closely related c-level skills (the body itself notes cro-advisor owns 'revenue math, NRR'), a minor but real conflict risk the description does not itself carve against.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

c-level-advisor/chief-customer-officer-advisor/skills/chief-customer-officer-advisor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.