CtrlK
BlogDocsLog inGet started
Tessl Logo

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./c-level-agents/skills/cro-review/SKILL.md
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 concise, well-structured forcing-questions skill with concrete thresholds and a usable output template. Its main weakness is a sparse workflow lacking explicit sequencing and validation checkpoints.

Suggestions

Turn the Workflow into explicit numbered steps (run scripts → gather metrics per question → fill output template → assign verdict) so the sequence is unambiguous.

Add a validation/verification checkpoint before issuing the verdict — e.g. confirm coverage and win-rate inputs are stage-weighted and from the last 4 quarters — to catch bad inputs early.

Note that the referenced revenue_forecast_model.py and churn_analyzer.py scripts live in the external cro-advisor skill, or bundle/localize them, so the workflow is self-contained.

DimensionReasoningScore

Conciseness

Lean and punchy throughout — six terse questions with concrete thresholds and no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Concrete thresholds (3x/4x, 90 days, 80%), executable script commands, and a full output template make it mostly actionable, though the workflow scripts live outside this skill's bundle.

4 / 5

Workflow Clarity

The workflow is just two sequential commands with no validation checkpoints, and the broader ask-then-fill-template process is implicit rather than laid out as explicit steps.

3 / 5

Progressive Disclosure

Well-organized into clear sections with self-contained content and clearly signaled one-level cross-skill links; no nested references, though no internal detail is split into bundle files.

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 tight, well-targeted description that clearly states the skill's purpose and concrete trigger conditions. It is specific and complete, with only marginal overlap risk against sibling review skills.

DimensionReasoningScore

Specificity

Names the revenue domain and four concrete subjects (revenue, win rate, NRR, ramp time) under a single vivid action ('Pipeline-paranoid interrogation'), giving several specific items with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('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.

5 / 5

Trigger Term Quality

Includes natural audience terms ('pipeline coverage', 'win rates drop', 'scaling the sales team', 'NRR', 'ramp time') that a CRO would actually say, with a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The CRO metric set (revenue/win rate/NRR/ramp) carves a distinct niche, with only minor overlap risk against sibling /cs:*-review skills (e.g. CFO/CMO).

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.