CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

revenue-operations

Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.

72

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, highly actionable skill body: runnable commands with sample data, complete input schemas, and four sequenced workflows with verification steps. The only weaknesses are minor — duplicated benchmark values across two sections and missing error-recovery guidance after cross-check steps.

Suggestions

Remove the duplicated benchmark targets from the GTM Efficiency Audit workflow (step 4) since the same values are already in the GTM Efficiency Calculator metrics table, and instead point to that table.

Add an error-recovery branch after each cross-check step (e.g., 'If totals don't match, re-export from CRM and re-run' ) to close the validation feedback loop in each workflow.

Consider consolidating the three per-tool Input Schema blocks into a single referenced file or the sample data files, since complete schemas for all three tools inline add ~90 lines to the main body.

DimensionReasoningScore

Conciseness

The body is dense with executable commands, input schemas, and benchmark tables rather than explanations of known concepts. Not 5: there is minor redundancy — benchmark targets ("Magic Number (>0.75)", "LTV:CAC (>3:1)", "CAC Payback (<18 months)", "Rule of 40 (>40%)") appear both in the GTM Efficiency Calculator table and again in the GTM Efficiency Audit workflow.

4 / 5

Actionability

Quick Start commands are copy-paste ready against verified real files (e.g., "python scripts/pipeline_analyzer.py --input assets/sample_pipeline_data.json --format text"), every tool has a complete JSON input schema, and concrete thresholds are given (coverage 3-4x, concentration >40%, MAPE rating bands).

5 / 5

Workflow Clarity

Each workflow is a clearly numbered sequence with explicit verification checkpoints ("Verify input data", "Cross-check output totals against your CRM source system", "Cross-check actuals against closed-won records"). Not 5: no error-recovery feedback loop is specified for what to do when a cross-check or reconciliation fails.

4 / 5

Progressive Disclosure

SKILL.md works as an overview with one-level-deep, clearly signaled references: the Reference Documentation table (revops-metrics-guide.md, pipeline-management-framework.md, gtm-efficiency-benchmarks.md) and Templates table all point to files verified to exist, and bulk detail is correctly kept in those bundle files.

5 / 5

Total

18

/

20

Passed

Description

92%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: third-person voice, concrete capability list, and an explicit 'Use when' clause with varied natural trigger phrases and synonyms. The only gap is a few missing natural terms (e.g., 'revenue operations', 'RevOps') that a user might say when requesting this skill.

DimensionReasoningScore

Specificity

"Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics" names multiple concrete capability areas that map one-to-one to the skill's three tools, with comprehensive coverage and no vague filler. Not 4: the action list covers the full toolset with no minor gaps.

5 / 5

Completeness

Explicitly answers both: what ("Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics") and when ("Use when analyzing sales pipeline coverage, forecasting revenue, ... measuring sales efficiency and unit economics for SaaS teams") with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The "Use when" clause lists natural phrases users would say — "analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, tracking forecast accuracy with MAPE" — including synonyms (go-to-market performance and GTM efficiency). Not 5: a few natural terms are missing, notably "revenue operations" / "RevOps" (the skill's own domain name) and "pipeline review".

4 / 5

Distinctiveness Conflict Risk

Clear niche in SaaS revenue operations with distinct triggers like "forecast accuracy with MAPE" and "unit economics for SaaS teams"; minimal overlap risk with generic analytics or CRM skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

business-growth/skills/revenue-operations/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.