CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

69

Quality

87%

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

The canonical home for this skill is cco-review in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

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 lean, highly actionable interrogation skill: exact thresholds, runnable commands, a concrete output template, and clean single-file organization. Its two weaker spots are unspecified input-file provenance for the referenced scripts and a workflow lacking explicit validation or feedback steps.

Suggestions

Specify where the script input files (cohorts.json, customers.json, book.json) come from — e.g., a one-line note on their expected schema or the command/source that generates them — to close the actionability gap.

Use stable paths for the three analyzer scripts (or reference them via the Related skill link) rather than fragile ../../../c-level-advisor/... relative traversal, so the Workflow commands remain executable regardless of where the skill is installed.

Add a brief validation checkpoint to the Workflow (e.g., what to do if a script errors or if GRR data is missing) to give the sequence an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is threshold-dense (GRR >= 90% at growth stage, 70/30 base/variable comp, $300K-$1M ARR/CSM tiers) with zero explanation of concepts Claude already knows; even the persona one-liners ('Not NRR. Gross.') encode decision rules, so every token earns its place.

5 / 5

Actionability

Copy-paste-ready script invocations, exact numeric cutoffs, and a fill-in output template make the guidance highly actionable, but the input files (cohorts.json, customers.json, book.json) have unspecified provenance and the cross-skill relative paths (../../../c-level-advisor/...) are fragile, leaving minor gaps.

4 / 5

Workflow Clarity

The Workflow section gives a clearly ordered 3-step sequence with an explicit start ('always start here') and a conditional gate ('if making CS team changes'), and the questions embed interpretation checkpoints ('If GRR < 85% but NRR > 100%... expansion is masking'), but there are no explicit validation or error-recovery steps.

4 / 5

Progressive Disclosure

A single-file skill cleanly sectioned (When to Run, Six Questions, Workflow, Output Format, Routing, Related) with clearly signaled one-level-deep external pointers (companion skill, agent file) and no bulk content inlined that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

83%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: explicit third-person 'what' with four named domains, a concrete 'Use when' clause, and natural persona-appropriate triggers. Its weaknesses are the single-action framing (no multi-action enumeration) and missing high-frequency synonyms like 'churn' and 'customer success'.

DimensionReasoningScore

Specificity

The description defines one precise action ('interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring') scoped across four explicitly enumerated domains, which is far more concrete than the anchor-3 example but does not list several distinct actions like the anchor-5 example.

4 / 5

Completeness

It explicitly answers both 'what' (Chief Customer Officer interrogation of plans touching retention, segmentation, CS sizing, or CS hiring) and 'when' with a concrete 'Use when' clause naming three specific triggers, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('gross retention is slipping', 'approving CSM headcount', 'customer segments to keep or fire'), but common variations a user would say — 'churn', 'customer success' spelled out, 'NRR' — are missing from the description.

4 / 5

Distinctiveness Conflict Risk

The niche (retention/CS-organization review) is clear with distinct triggers, but within its family of sibling C-level review skills, 'gross retention slipping' could overlap with a CRO review and 'CS team hiring' with a CHRO advisor, leaving minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cco-review/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.