cro-review
$
npx mdskill add alirezarezvani/claude-skills/cro-reviewAnalyzes CRO metrics to identify revenue risks and scaling readiness
- Evaluates pipeline coverage, win rate, NRR, and ramp time for forecasting accuracy
- Requires access to sales data, quota performance, and stage conversion metrics
- Applies growth-stage benchmarks to detect early warning signs in sales health
- Returns prioritized action items for improving pipeline reliability and sales efficiency
SKILL.md
.github/skills/cro-reviewView on GitHub ↗
--- name: "cro-review" description: "/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." --- # /cs:cro-review — CRO Forcing Questions **Command:** `/cs:cro-review <plan>` The pipeline-paranoid operator pressure-tests revenue assumptions. Six questions that surface next-quarter pain this quarter. ## When to Run - Before committing to a quarterly revenue target - Before changing sales motion (PLG ↔ sales-led, mid-market ↔ enterprise) - Before hiring a batch of reps - When pipeline coverage drops below 3x - When NRR is trending down ## The Six CRO Questions ### 1. Pipeline Coverage **What is pipeline coverage for the current quarter, by stage?** - Inbound-heavy: 3x. Outbound-heavy: 4x. Below either threshold = act now. - Stage-weighted, not just total. ### 2. Win Rate Trajectory **What's win rate this quarter vs the last 4 — and what's the leak point?** - Stage-by-stage conversion. - If a single stage softens, identify why before forecasting. ### 3. NRR Decomposition **What's gross retention, contraction, and expansion separately?** - NRR alone hides churn. - A 110% NRR with 95% gross retention is different from 110% with 80%. ### 4. Ramp Time **For the last 4 hires, how many days to first deal and to quota?** - If ramp > 90 days at growth stage, hiring profile or enablement is broken. - Forecasted hires must build in ramp. ### 5. Discount Discipline **What's the median discount this quarter vs last 4? Where is it creeping?** - Discount creep is the leading indicator of pricing or positioning weakness. - Cap discounts by approver tier. ### 6. Pipeline Source Mix **What % of pipeline is marketing-sourced, sales-sourced, partner-sourced?** - If one source dominates > 80%, you have concentration risk. - Cross-check with cs-cmo-advisor. ## Workflow ```bash python ../../../skills/cro-advisor/scripts/revenue_forecast_model.py python ../../../skills/cro-advisor/scripts/churn_analyzer.py ``` ## Output Format ```markdown # CRO Review: <plan> **Date:** YYYY-MM-DD ## Pipeline - Coverage: X.Xx (target 3x+) - Win rate: X% (4Q trend: ↑ / → / ↓) - Top leaking stage: <name> ## Retention - Gross retention: X% - NRR: X% - Expansion: X% - Contraction: X% ## Ramp - New hires last quarter: N - Median days to first deal: X - Median days to quota: X ## Discount - Median discount this quarter: X% - Trend vs 4Q ago: <delta> ## Source Mix - Marketing: X% | Sales: X% | Partner: X% ## Verdict 🟢 ON PLAN | 🟡 GAP | 🔴 PIPELINE CRISIS ## Next Steps [3 concrete actions] ``` ## Routing - `/cs:cfo-review` — does this hit the cash plan? - `/cs:cmo-review` — is pipeline source-mix healthy? - `/cs:execute` — quarterly plan if GREEN - `/cs:boardroom` — if RED ## Related - Agent: [`cs-cro-advisor`](../../agents/cs-cro-advisor.md) - Skill: [`cro-advisor`](../../../skills/cro-advisor/SKILL.md) - Execution: `../../../../business-growth/` --- **Version:** 1.0.0
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.