CtrlK
BlogDocsLog inGet started
Tessl Logo

revops

Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/revops/SKILL.md

The canonical home for this skill is revops in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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, actionable RevOps reference with strong progressive disclosure via four real bundle files. The main weakness is verbosity in the principles prose and implicit validation checkpoints in the workflow.

Suggestions

Tighten the Core Principles section: replace axiomatic explanations ('If data lives in multiple places, it will conflict') with the operational rule alone, trusting Claude's background knowledge.

Add explicit validation gates to the workflow — e.g., after drafting lifecycle/scoring specs, a checkpoint to confirm definitions are agreed across marketing, sales, and CS before moving to automation design.

Consider moving the enrichment-tool comparison table and quarterly audit checklist into a references file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly useful reference material (tables, thresholds, benchmarks), but the Core Principles section pads with axioms Claude already knows ('If data lives in multiple places, it will conflict', 'Automating a broken process just creates broken results faster') that could be trimmed.

3 / 5

Actionability

Delivers concrete, executable guidance — specific SLAs (4hr/48hr), speed-to-lead (5 min), ACV thresholds ($25K), point ranges (50-80), approval tiers, and a 5-document output spec — with only minor gaps.

4 / 5

Workflow Clarity

Sequences the work (gather 6 context inputs → apply frameworks → deliver 5 outputs; 6-step scoring model with a 'test against historical data' checkpoint), but most validation checkpoints are implicit rather than gated.

3 / 5

Progressive Disclosure

SKILL.md is a clear overview with four well-signaled one-level-deep references (lifecycle-definitions, scoring-models, routing-rules, automation-playbooks), all of which exist as real files, making navigation easy.

5 / 5

Total

15

/

20

Passed

Description

88%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 states concrete capabilities and an explicit 'Use when' trigger in third-person voice. Minor room to add common synonyms (RevOps, SLA) and sharpen distinctiveness from sibling GTM skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'lead lifecycle rules, scoring, routing, handoffs, and CRM process automation' — covering the domain comprehensively rather than gesturing at it.

5 / 5

Completeness

Explicitly answers both what ('Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation') and when ('Use when marketing, sales, and customer success workflows need clearer operational structure').

5 / 5

Trigger Term Quality

Includes natural terms users would say ('marketing, sales, and customer success workflows', 'lead lifecycle', 'scoring', 'routing', 'handoffs') but misses some synonyms and shorthand like 'RevOps' or 'SLA'.

4 / 5

Distinctiveness Conflict Risk

Revenue operations is a clear niche with distinct triggers, with only minor overlap risk against closely related skills like sales-enablement and pricing-strategy.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.