Content
42%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a comprehensive RevOps handbook than a focused skill for Claude. It extensively explains domain concepts Claude already understands (what MQLs are, how lead scoring works, pipeline metrics) rather than providing targeted, actionable instructions for specific tasks. The referenced bundle files don't exist, and the main file contains far too much inlined content that should be delegated to supporting documents.
Suggestions
Cut 60-70% of the conceptual content (lifecycle definitions, scoring concepts, metric benchmarks) that Claude already knows, and focus on the specific decision-making rules and output templates Claude should follow when helping users.
Add concrete output examples — show what a completed lifecycle stage document, scoring specification, or routing rules document should actually look like rather than just listing deliverable names.
Create the referenced bundle files (lifecycle-definitions.md, scoring-models.md, routing-rules.md, automation-playbooks.md) and move the detailed tables and frameworks there, keeping SKILL.md as a concise overview with clear navigation.
Add explicit validation steps to the workflow — e.g., after drafting a scoring model, verify it against the user's historical data; after defining lifecycle stages, confirm alignment with the user's team structure before proceeding to routing rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is significantly verbose at ~350+ lines, extensively explaining RevOps concepts (lifecycle stages, scoring dimensions, pipeline metrics, deal desk processes) that are general business knowledge Claude already possesses. Much of this reads like a RevOps textbook rather than targeted instructions for Claude. Tables of benchmarks, enrichment tool descriptions, and metric definitions are padding that doesn't add actionable value. | 2 / 5 |
Actionability | The skill provides structured frameworks (lifecycle tables, scoring dimensions, routing methods) and some concrete guidance like SLA timeframes and approval tiers, but lacks executable code, specific CRM configuration steps, or copy-paste ready templates. The output format section lists deliverables but doesn't show examples of what they should look like. Guidance remains at the conceptual/framework level rather than truly executable. | 3 / 5 |
Workflow Clarity | The 'Before Starting' section provides a reasonable intake sequence, and the scoring model section has a numbered build process. However, there are no validation checkpoints or feedback loops for the overall RevOps design process. The skill describes what to produce but doesn't clearly sequence how to move from intake through delivery with verification steps. The 'Define Before Automate' principle hints at validation but isn't operationalized into the workflow. | 3 / 5 |
Progressive Disclosure | The skill references four separate files (lifecycle-definitions.md, scoring-models.md, routing-rules.md, automation-playbooks.md) which is good structure, but none of these bundle files actually exist (no bundle provided). The main file itself is a monolithic wall of content that should have more aggressively pushed detail into those reference files. The inline content is far too extensive for what should be an overview document pointing to detailed references. | 3 / 5 |
Total | 11 / 20 Passed |