CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

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

The canonical home for this skill is revenue-operations in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable with executable commands, full input schemas, and well-sequenced validation-checked workflows. Its main weakness is progressive disclosure: it points to reference, script, and asset files that are not present in the bundle.

Suggestions

Ship the referenced bundle files (references/*.md, scripts/*.py, assets/*) so the navigation links in the Reference Documentation and Templates tables resolve, or remove the broken links.

Move the three full inline JSON input schemas into the sample asset files (e.g. assets/sample_*.json) and keep only minimal examples in SKILL.md to reduce token redundancy with the repeated Usage blocks.

Add an explicit validate->fix->retry feedback loop to the workflows (e.g. 'if the cross-check fails, correct the input export and re-run') to lift workflow clarity to 5.

DimensionReasoningScore

Conciseness

Mostly efficient with no basic-concept padding, but the per-tool 'Usage' blocks repeat the Quick Start commands and the three full inline JSON input schemas add tokens that could be trimmed or moved to references.

4 / 5

Actionability

Fully copy-paste-ready executable commands with --format flags, complete JSON input schemas, formula tables, and accuracy-rating tables cover the common cases concretely.

5 / 5

Workflow Clarity

Four numbered workflows with explicit validation checkpoints ('Verify input data', 'Cross-check ... before proceeding/conclusions/sharing'), but no validate->fix->retry feedback loop for error recovery, capping it below 5.

4 / 5

Progressive Disclosure

Structure and signaling are good (reference/template tables, one-level-deep pointers), but the referenced references/, scripts/, and assets/ files do not exist in the bundle, so the promised navigation targets are broken and substantial reference material is inlined.

3 / 5

Total

16

/

20

Passed

Description

95%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 with an explicit 'Use when' clause and comprehensive natural trigger terms tailored to a specialized SaaS RevOps niche. The only minor gap is that the stated capabilities are somewhat homogeneous variants of analysis rather than a diverse action set.

DimensionReasoningScore

Specificity

Names the SaaS revenue domain and several concrete analytic actions ('Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics'), but the actions are variations on analyzing/evaluating rather than the broad multi-verb coverage of the 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (analyzes pipeline health, forecast accuracy, GTM efficiency) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms with synonyms ('sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, ... tracking forecast accuracy with MAPE, calculating GTM efficiency, ... unit economics') covering what a SaaS RevOps user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (SaaS revenue operations) with distinct specialized triggers (MAPE forecast accuracy, GTM efficiency, pipeline coverage) that minimize overlap with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing

Warning

referenced_paths_exist

Referenced path issues: 23 missing

Warning

Total

14

/

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.