Conciseness

The body is dense with actionable specifics and never explains concepts Claude already knows (no 'what is an OKR' padding), so it clears anchor 3. It falls short of anchor 5's every-token-earns-its-place bar because the ~190-line body has trimmable material — the 'Receipts' quotes duplicate references/quotes.md and nearly every bullet carries a guest attribution that could be slimmed in places.

Actionability

For an instruction-only skill the guidance is fully executable: a situation-routing table for play selection, a concrete scoring procedure with numeric confidence caps by evidence type, a willingness-to-pay check with subset sizes, a pasteable deliverable template, and a 1/3/5 grading rubric — matching anchor 5's copy-paste-ready coverage of common cases. Anchor 4 would require missing key details, and none are evident.

Workflow Clarity

The sequence Diagnose (capped at 4 questions) → Pick the play (routing table) → Run it (plays A-E) → Deliverable → Grade is explicit, and each play ends with a 'Done when:' validation checkpoint, with red flags for error detection and 'adjust after small tests' feedback loops — matching anchor 5's explicit validation and checklists. Not anchor 4: checkpoints are present across every play rather than only most.

Progressive Disclosure

Both references (references/frameworks.md, references/quotes.md) are real files, one level deep, and clearly signaled with one-line descriptions in the 'Go deeper' section, matching most of anchor 5. It sits at anchor 4 because the body is long for an overview and the 'Receipts' section duplicates content that already lives in references/quotes.md — a minor organization gap.

Specificity

"Turns a pile of ideas, requests and goals into a confidence-scored roadmap plus a goals/OKR set" names several concrete deliverables (confidence-scored roadmap, goals/OKR set), which goes beyond the 1-2 generic actions of anchor 3. It stops short of anchor 5 because the capabilities are compressed into a single transformation verb rather than an enumeration of the distinct plays (scoring, roadmapping, OKR writing) the skill actually runs.

Completeness

The first sentence explicitly states what the skill does ("Turns a pile of ideas... into a confidence-scored roadmap plus a goals/OKR set") and the second gives an explicit "Use when someone says..." clause with concrete trigger phrases — the exact pattern of the anchor 5 example. It is not anchor 4 because the 'when' guidance is fully explicit rather than only partially specific.

Trigger Term Quality

The description packs in nine natural quoted trigger phrases users would actually say — 'prioritize', 'what should we build next', 'roadmap', 'now next later', 'ICE or RICE', 'write our OKRs', 'quarterly planning', 'too many priorities', 'sales keeps changing the plan' — including colloquial variants, matching the comprehensive synonym coverage of anchor 5. Anchor 4 would apply only if common variations were missing, and none obviously are.

Distinctiveness Conflict Risk

Triggers like 'now next later', 'ICE or RICE' and 'too many priorities' carve a clear prioritization niche, but broader triggers ('roadmap', 'what should we build next', 'quarterly planning') have minor overlap risk with closely related planning skills — the body itself lists adjacent skills such as 'strategy' and 'ai-product-bets'. This matches anchor 4 (mostly distinct, minor overlap with closely related skills) better than anchor 5's minimal-conflict bar.