The body uses compact tables, a copy-paste markdown template, and bullet lists without explaining concepts Claude already knows, matching the 'Lean and efficient; every token earns its place' anchor rather than the padded score 2 example.

It provides a copy-paste-ready markdown template and two concrete executable commands ('git diff --name-only -- *.md' and 'gh pr view <PR_NUMBER> --json additions,deletions,changedFiles'), matching the 'Fully executable code/commands; copy-paste ready' anchor.

The default template gives a sequenced Quick path (First action, Second action, Verification) plus a Checklist, and there are no destructive/batch operations requiring validation; per the simple-skills note, clear well-organized content scores 3.

The body is under 50 lines with no bundle files and no need for external references, organized into well-signaled sections (When to Use, Critical Patterns, Documentation Shape, PR and Review Docs, Commands), meeting the simple-skills exception for score 3 on organization alone.

Quotes 'Design docs that reduce cognitive load' and a list of doc types name the domain and a concrete action, but do not enumerate multiple distinct concrete capabilities, matching the 'Names domain and some actions, but not comprehensive' anchor rather than the multi-action score 3.

It answers what ('Design docs that reduce cognitive load') and when via an explicit 'Trigger:' clause, matching the score 3 anchor that requires both what and explicit triggers; the presence of an explicit trigger clause means it is not capped at 2.

'Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs' provides strong coverage of natural terms a user would actually say, matching the score 3 anchor for good keyword coverage.

The cognitive-load framing is a distinct niche, but the broad 'docs' domain could still overlap with general writing/documentation skills, matching the score 2 'Somewhat specific but could still overlap' anchor rather than a clearly non-conflicting score 3.