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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

86%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, highly actionable skill body that uses scripts and references effectively with clear workflows. The main improvement areas are tightening the Keywords/disclaimer padding and making workflow validation checkpoints explicit.

Suggestions

Trim or collapse the long Keywords paragraph (consider moving it into a reference file or a metadata field) to reduce token load without losing trigger coverage.

Add an explicit validation step to each workflow (e.g. 'Verify the tool's health verdict against your known top-3 churn drivers before acting') so checkpoints are gates, not implicit cross-checks.

Cut the trailing Version/Status/Disclaimer boilerplate or move it into frontmatter metadata, since it does not guide execution.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and assumes Claude's competence (no basic concept explanations), but the lengthy Keywords block and the trailing Disclaimer/version boilerplate could be trimmed. It is efficient with minor instances of over-explanation rather than lean throughout.	4 / 5
Actionability	Quick Start gives copy-paste-ready commands with embedded samples (scripts run with no args), threshold/coverage tables are concrete, and each script exposes a documented JSON input schema — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Four workflows are numbered with goals, time estimates, cross-checks against adjacent advisors, and explicit output specs, but validation checkpoints are implicit (cross-checks) rather than explicit validate-then-proceed gates.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-signaled, one-level-deep references to four real reference files and three real scripts ('See references/X for ...'), all of which exist on disk; navigation is easy and nothing is nested deeper than one level.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific, third-person description with explicit 'what' and 'when' guidance and clear boundary signaling against adjacent skills. The only minor gap is trigger-term synonym coverage in the 'Use when' clause.

Dimension	Reasoning	Score
Specificity	Lists four concrete capabilities — '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' — each with specific sub-actions, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (the four advisory decisions with detail) and 'when' ('Use when designing retention strategy, segmenting customers... sizing CS team, or sequencing CS hires') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when designing retention strategy, segmenting customers for differential investment, sizing CS team, or sequencing CS hires' clause supplies natural trigger phrases a user would actually say, but a few common synonyms (e.g. churn, NRR, book of business) are absent from the trigger clause itself.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear CCO-advisory niche and explicitly states 'does not duplicate engineering/business-growth tactical skills', minimizing overlap with adjacent tactical skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 19392f7

Reviewed: ~5 hours ago

Table of Contents

Discovery Implementation Validation

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.