Conciseness

The body is mostly efficient — dense tables and skill-specific thresholds (4-hour/48-hour SLAs, discount approval tiers) — but it recites standard RevOps knowledge Claude already has (MQL/SQL funnel definitions, BANT-style opportunity criteria, CAC/LTV:CAC benchmarks, published speed-to-lead statistics) and duplicates context-gathering questions across 'Before Starting' and 'Task-Specific Questions.' This matches the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is not padded enough for 2, and the generic-knowledge recitation and redundancy rule out 4.

Actionability

As an instruction-only skill it provides concrete, specific guidance: SLA timings ('contacts within 4 hours... qualifies or rejects within 48 hours'), discount approval tiers by deal size, stage tables with entry/exit criteria and required fields, metric formulas with benchmarks, and an Output Format specifying five concrete deliverables. It falls short of the 5 anchor because there are no worked examples of those deliverables (e.g., a sample routing decision tree or scoring spec) and some sections are consideration lists rather than executable steps.

Workflow Clarity

Sequences exist in places — the scoring-model build is well ordered with validation and rollback ('freeze the rule and test a later, fully observed holdout... pilot with monitoring and rollback') and 'Before Starting' orders context gathering — but the skill as a whole is a set of parallel domain modules with no unified end-to-end sequence connecting diagnosis to design to delivery, and checkpoints are mostly implicit. This matches the 3 anchor; the 4 anchor requires a clear overall sequence with most checkpoints present. No destructive/batch cap applies.

Progressive Disclosure

Five real reference files (lifecycle-definitions, scoring-models, routing-rules, inbound-routing, automation-playbooks) are each clearly signaled with purpose ('For complete lifecycle stage templates and SLA examples: See references/lifecycle-definitions.md'), all body paths resolve to actual files, and references are one level deep (only external URLs inside them). Content is appropriately split (~350-line overview body vs. ~1,100 lines of detail in references) with well-organized sections, matching the 5 anchor.

Specificity

The description enumerates many specific sub-capabilities ('lead scoring,' 'lead routing,' 'deal desk,' 'CRM automation,' 'data hygiene,' 'pipeline management'), going well beyond naming 1-2 actions, but the verbs are generic ('wants help with') and never state what the skill actually does (design, optimize, audit). It sits between the 3 anchor (domain plus 1-2 concrete actions) and the 5 anchor (multiple concrete action verbs with comprehensive coverage), so 4 fits best.

Completeness

Both questions are explicitly answered: the 'what' ('help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes') and a highly explicit 'when' ('Use when the user wants... Also use when the user mentions...') with concrete trigger phrases. The explicit 'Use when' clause is present so no cap applies, and the 4 anchor's weakness (a 'when' that could be more explicit) does not apply here.

Trigger Term Quality

Sixteen explicit quoted trigger phrases include synonyms ('RevOps,' 'revenue operations'), acronyms ('MQL,' 'SQL'), and natural user phrasings ('leads aren't getting to sales,' 'when should marketing hand off to sales'). This matches the 5 anchor's comprehensive synonym coverage; it is clearly above the 4 anchor, which expects a few natural terms missing.

Distinctiveness Conflict Risk

A clear RevOps niche with distinct triggers, plus explicit disambiguation pointers ('For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.') that reduce conflict with neighboring marketing skills. Minimal overlap risk, matching the 5 anchor.