cco-review

/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.

Quality

85%

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

82%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 CCO interrogation framework with concrete thresholds, executable script calls, and a complete output template. Its main weakness is that the referenced scripts are external paths with no local bundle, so progressive disclosure and verifiability of those references are slightly undercut.

Suggestions

Add an explicit verification checkpoint in the Workflow (e.g., confirm each script's JSON output parsed and has non-empty cohorts before proceeding to the next step).

Either vendor the three referenced scripts into a local ./scripts/ bundle or document their expected input/output schema inline so the commands are verifiable without the external skill.

Trim the duplicate link lists in Routing and Related, consolidating cross-references into one section to tighten token usage.

Dimension	Reasoning	Score
Conciseness	Dense and punchy throughout ("Not NRR. Gross.", threshold tables) with little concept padding; a few explanatory asides and the repeated Routing/Related link lists could be trimmed slightly.	4 / 5
Actionability	Provides concrete thresholds (GRR ≥ 90%, 70/30 comp, ARR-per-CSM bands), named scripts with arguments, executable bash commands, and a copy-paste-ready output template covering the common decision cases.	5 / 5
Workflow Clarity	The Workflow is a clear numbered 3-step sequence with a conditional gate ("if making CS team changes"); it lacks explicit validate/verify checkpoints, but the operations are read-only analysis rather than destructive or batch, so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clear sections (When to Run, Six Questions, Workflow, Output Format, Routing, Related) with one-level-deep, clearly signaled references; the cited scripts live as external relative paths outside this bundle rather than as local bundle files, a minor structural gap.	4 / 5
	Total	17 / 20 Passed

Description

87%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 crisply states a narrow CCO-retention niche and pairs it with explicit, natural-sounding 'Use when...' triggers covering both what and when. Minor room to add a couple of synonym triggers (churn, NRR) for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete touch points ("customer retention, segmentation, CS team sizing, or CS team hiring") with a specific action frame ("interrogation"), though the verbs themselves stay somewhat abstract rather than enumerating distinct operations.	4 / 5
Completeness	Explicitly answers both what ("Retention-obsessed Chief Customer Officer interrogation of any plan that touches...") and when ("Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a CCO/exec would actually say ("gross retention is slipping", "approving CSM headcount", "customer segments to keep or fire"); coverage is strong but a few synonymous triggers (e.g. churn, NRR) are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (CCO retention interrogation) with distinct, specific triggers that are unlikely to fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: c-level-agents/skills/cco-review/SKILL.md
Commit: 19392f7

Reviewed: ~11 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.