cro-advisor

Revenue leadership for B2B SaaS companies. Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building board forecasts, or when user mentions CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity.

Quality

95%

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

93%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 dense, expert-calibrated advisory skill that gives Claude precise revenue benchmarks and concrete commands without padding, and cleanly routes detail into real reference files. The only gap is workflow sequencing, which is distributed rather than presented as a numbered, checkpointed procedure.

Suggestions

Add one numbered 'Engagement workflow' (e.g. 1. Read company-context.md 2. Run diagnostic questions 3. Select framework from Core Responsibilities 4. Produce Output Artifact 5. Pass through Internal Quality Loop) to elevate workflow_clarity from 4 to 5.

Note that the 'Keywords' line largely duplicates the description's trigger terms; if token budget tightens, fold the unique terms into the description and drop the standalone list.

Dimension	Reasoning	Score
Conciseness	Lean and information-dense — it assumes Claude's competence, never explains what NRR/quota/Magic Number are, and every table and benchmark (e.g. 'NRR > 110%', 'Magic Number > 0.75', 'CAC Payback < 18 months') earns its place by encoding precise thresholds Claude would not reliably produce alone.	5 / 5
Actionability	Fully actionable: concrete CLI commands ('python scripts/revenue_forecast_model.py'), exact diagnostic questions to ask, specific metric targets and red-flag thresholds, and an Output Artifacts table mapping requests to concrete deliverables.	5 / 5
Workflow Clarity	A clear sequence is implied (diagnostic questions → framework → output artifact → Internal Quality Loop) with an explicit validation/feedback loop in the Communication section, but it lacks a rigidly numbered step sequence with per-step checkpoints that would warrant a 5.	4 / 5
Progressive Disclosure	SKILL.md is a genuine overview with well-signaled, one-level-deep references — the Core Responsibilities table and Resources section each point to real bundle files (sales_playbook.md, pricing_strategy.md, nrr_playbook.md, the two scripts) with a one-line description of what each contains.	5 / 5
	Total	19 / 20 Passed

Description

96%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, third-person description that clearly states capabilities and provides a rich, synonym-covered 'Use when' trigger clause. Its only weakness is that several broad trigger terms could overlap with neighboring sales, pricing, or retention skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling' plus 'setting quotas, modeling NRR, evaluating pricing, building board forecasts' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (revenue leadership capabilities) and 'when' via a clear 'Use when designing... or when user mentions...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms — 'CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity' — matching phrasings a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The CRO/revenue-leadership niche is mostly distinct, but broad terms like 'pricing strategy', 'churn', and 'sales model' carry minor overlap risk with adjacent pricing, customer-success, or sales-ops skills; not a 5 because conflict risk is not fully minimal.	4 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: c-level-advisor/skills/cro-advisor/SKILL.md
Commit: 19392f7

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