Name: cro-advisor
Rating: 66.4 (1 reviews)
Author: alirezarezvani

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cro-advisor/SKILL.md

The canonical home for this skill is cro-advisor in alirezarezvani/claude-skills

Quality

Content

60%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.

The body is well-structured with actionable formulas, benchmarks, and CLI entry points, but it leans on assumed-available bundle files that are absent, and its multi-step workflows omit explicit validation checkpoints. Conciseness is decent yet padded with role-conventional knowledge.

Suggestions

Add explicit ordered workflows with validation checkpoints (e.g., forecast → sanity-check coverage/assumptions → flag anomalies → revise) to lift workflow_clarity above the batch-operation cap of 3.

Ship the referenced bundle files (references/sales_playbook.md, references/pricing_strategy.md, references/nrr_playbook.md, scripts/revenue_forecast_model.py, scripts/churn_analyzer.py) or remove the pointers so progressive disclosure is genuinely navigable.

Trim inferred role-conventional content (the full 'Integration with Other C-Suite Roles' table and 'Communication'/'Context Integration' sections) to focus tokens on revenue-specific guidance Claude does not already know.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and terse bullets, but the 'Integration with Other C-Suite Roles' table and 'Communication'/'Context Integration' sections restate role-common knowledge (e.g., bottom-line-first output, reading company-context) that a competent Claude can infer.	3 / 5
Actionability	Concrete CLI invocations ('python scripts/revenue_forecast_model.py') and formula definitions ('Magic Number: Net New ARR × 4 ÷ Prior Quarter S&M Spend') with benchmark targets, though the referenced scripts are absent and several tables describe rather than instruct.	4 / 5
Workflow Clarity	Sequences are implicit (diagnostic questions → framework → artifact) with no explicit ordered procedure, and forecast/churn batch operations lack a validate-fix-retry loop, which caps the score at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	Good section structure and one-level-deep pointer lines to references/sales_playbook.md etc., but every referenced file (references/.md, scripts/.py) is missing from the bundle, so the promised progressive disclosure is not actually navigable.	3 / 5
	Total	13 / 20 Passed

Description

100%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, specific description that names concrete revenue-leadership capabilities and pairs them with an explicit, comprehensive 'Use when...' clause covering natural trigger terms and synonyms. It is concise, third-person, and clearly distinguishable from adjacent C-suite skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling' — giving comprehensive coverage of CRO capabilities.	5 / 5
Completeness	Explicitly answers both what ('Revenue forecasting, sales model design, pricing strategy...') and when ('Use when designing the revenue engine, setting quotas, modeling NRR...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and acronyms users say: 'CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity'.	5 / 5
Distinctiveness Conflict Risk	Clear niche (CRO/revenue leadership) with distinct triggers; the 'chief revenue officer' framing minimizes overlap with adjacent finance or sales-rep skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	15 / 16 Passed

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

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