CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cpo-review

/cs:cpo-review <plan> — JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus. Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve.

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

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 well-structured, token-efficient review skill with concrete commands and a strong output template. The gaps are operational: script invocations lack arguments, and the workflow has no explicit validation or data-availability checkpoint.

Suggestions

Show the expected invocation for each analysis script, including arguments (e.g., input plan path or feature list), so the commands are copy-paste ready rather than bare paths.

Add a validation checkpoint in the Workflow, e.g. a minimum cohort sample size before judging a retention curve 'decaying', and an instruction for what to do when PMF/retention data is unavailable.

Map each script's output to the question it answers (e.g., 'pmf_scorer.py → Question 3; rice_prioritizer.py → Question 4') so the analyses visibly feed the six questions.

DimensionReasoningScore

Conciseness

The body is lean and punchy — questions are 2-3 lines with calibration examples ("Not 'improve onboarding.'"), and it never explains concepts Claude already knows (no JTBD or RICE primer). Every section earns its tokens; matches anchor 5 rather than 4, which requires trims.

5 / 5

Actionability

Includes runnable commands ("python ../../../c-level-advisor/skills/cpo-advisor/scripts/pmf_scorer.py") and a concrete fill-in-the-blank output template with a verdict enum. Not 5: the script commands take no arguments, and nothing ties each script's output to the specific question it informs.

4 / 5

Workflow Clarity

The Workflow section sequences run-analyses → answer-questions → apply-verdict with the output template acting as a checklist (cohort sample size, thresholds, verdict). Not 5: there is no explicit validation or recovery step (e.g., what to do when retention data or a script is unavailable), leaving checkpoints implicit.

4 / 5

Progressive Disclosure

No bundle files exist, and the self-contained ~105-line body is well-sectioned with nothing that belongs in a separate file; the Related/Routing links are clearly signaled and one level deep. Matches anchor 5's clear overview and easy navigation.

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 with explicit what and when clauses and natural, role-appropriate trigger phrases. Its only weaknesses are the single abstract verb describing the actions and reliance on the "PMF" acronym without spelled-out synonyms.

DimensionReasoningScore

Specificity

"JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus" names several specific analysis targets, going beyond a bare domain label, but a single abstract verb ("interrogation") covers them all rather than listing distinct concrete actions. Fits anchor 4 (several specific items, minor gaps) better than 5 (multiple concrete actions, comprehensive) or 3 (only 1-2 concrete actions).

4 / 5

Completeness

Both parts are explicit: "JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus" answers what, and "Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve" answers when with three concrete trigger scenarios. This matches the anchor-5 pattern; not 4 because the 'when' is already explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Natural CPO phrases like "committing a quarter's roadmap", "kill a feature", and "retention curve" are present, but "PMF" appears only as an acronym — the spelled-out "product-market fit" and synonyms like "roadmap review" are missing. Good coverage with a few natural terms absent, matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

The specialized vocabulary (JTBD, PMF signal, portfolio focus) carves a distinct CPO niche, but "product roadmap" is broad enough to overlap with generic product-management skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than 5's minimal-conflict profile.

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

c-level-agents/skills/cpo-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.