CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cro-review

/cs:cro-review <plan> — Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time. Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team.

66

Quality

83%

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 cro-review in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 tight, high-signal interrogation checklist with concrete thresholds and a fully specified output template, weakened mainly by an underspecified Workflow section: two argument-less script invocations with no sequencing, no tie-in to the six questions, and no validation of metric availability before the verdict. Progressive disclosure is good but leans on external skill paths.

Suggestions

Sequence the Workflow section: state when each script runs relative to the six questions, what inputs it takes (pass the <plan> data or path), and which section of the output template its results populate.

Add a validation checkpoint before the verdict, e.g., confirm data exists for all six metrics and explicitly flag any unavailable metric as a GAP rather than estimating it.

Either include the analysis scripts in this skill's own scripts/ directory or explain what the external cro-advisor scripts produce and how their output feeds the report, so the commands are self-contained and executable.

DimensionReasoningScore

Conciseness

The body is lean bullet guidance with concrete thresholds ("Inbound-heavy: 3x. Outbound-heavy: 4x", "ramp > 90 days", "dominates > 80%") and no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Each question pairs with interpretation rules and numeric thresholds, and the output template is fully specified, but the Workflow section's two bare python commands take no arguments — the <plan> input never reaches them and their role relative to the six questions is unstated — a minor gap against the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The sequence (run scripts → answer six questions → render template → route by verdict) is present but implicit: the Workflow section lists two commands with no sequencing context, and there are no validation checkpoints (e.g., confirming data exists for each metric before issuing the verdict). This is an analytical skill, so the destructive-operation cap does not apply, but checkpoints are missing rather than minor, which holds it at anchor 3.

3 / 5

Progressive Disclosure

Well-organized sections (When to Run, Questions, Workflow, Output Format, Routing, Related) with clear one-level cross-references and no bundle files needed, but the script paths point outside the skill into another skill's directory, a minor navigation gap against the ideal split.

4 / 5

Total

16

/

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 that pairs concrete metric interrogation with an explicit "Use when..." trigger clause in third person. It is comprehensive on the four headline metrics but omits discount and source-mix coverage and lacks a few natural synonyms (churn, ARR).

DimensionReasoningScore

Specificity

"Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time" lists several specific metric-level actions, but omits coverage the body actually provides (discount discipline, pipeline source mix), so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both "what" ("Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time") and "when" ("Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Triggers like "forecast misses pipeline coverage", "win rates drop", and "scaling the sales team" are natural user phrases with good coverage, but common synonyms such as churn, ARR, retention, and quota are absent.

4 / 5

Distinctiveness Conflict Risk

CRO-specific terms (pipeline coverage, win rates, NRR) carve a clear niche, but "forecast" creates minor overlap risk with closely related finance-planning skills like a CFO review.

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/cro-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.