Conciseness

The same canonical stat is restated five times — "Prosci research shows 5–7 touchpoints are the floor" (Purpose), "assess whether 5–7 touchpoints are scheduled" (When to use), "Prosci's documented floor for behavioral change is 5–7" (Scripts), "Prosci floor is 5–7" (Anti-patterns), "minimum 5, target 7" (forcing-question 3) — and the manager-trust and magnitude-honesty points are likewise each repeated across 3–4 sections. That is more than the 'minor instances of over-explanation' of anchor 4, fitting anchor 3 ('could be tightened'), though the content is domain-specific with no generic-concept padding, so it is not the severe verbosity of anchor 2.

Actionability

Concrete executable command ("cd business-operations/skills/internal-comms && python3 scripts/comms_template_filler.py --sample"), specific script flags verified in the actual argparse code (--input, --output, --sample, --profile with the exact profile enum), and concrete recommended answers per forcing question. It misses anchor 5 because only one of the three scripts has an example invocation and the example's cd path assumes a fixed install location rather than being copy-paste ready relative to the skill.

Workflow Clarity

"Five-step deterministic flow. Follow in order." gives a clear numbered sequence with concrete per-step commands, and step 5 is an explicit pre-publish validation gate ("any one of them is a 'do not send' signal") with tool-enforced validations in step 2. It falls short of anchor 5 because the error-recovery feedback loop is implicit — the sweep says what fails but never says what to do next (fix which artifact, re-run which script) — though it is clearly above anchor 3, where checkpoints are merely listed without an explicit gate.

Progressive Disclosure

References are one level deep, well-signaled with per-file descriptions, and all six referenced paths (3 references, 3 scripts, 1 asset template) verified to exist; each script section documents purpose and flags rather than inlining the code. Minor gaps keep it below anchor 5: the ~30-line forcing-question library with full recommended answers and citations, and the anti-pattern list that previews the references file's 8 anti-patterns, are detail that arguably belongs in a reference file with a pointer from the overview.

Specificity

Lists multiple concrete deliverables — "produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points" — plus the concrete tuning mechanism "industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}". This matches the anchor for comprehensive concrete-action coverage; it is well above anchor 4, which only requires 'several specific actions with minor gaps'. Voice is third person ("Pairs...", "produce...").

Completeness

Explicitly answers 'what' (pairs ADKAR and Kotter with deterministic tools to produce the four named artifacts) and 'when' ("Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to..." plus a dedicated "Triggers on..." clause with concrete trigger phrases). This is a direct match to the anchor-5 exemplar structure; anchor 4 ('when could be more explicit') clearly fits worse given two explicit trigger formulations.

Trigger Term Quality

Explicit triggers — "all-hands announcement", "change comms", "rollout comms", "re-org announcement", "manager talking points", "layoff comms" — are natural phrases a comms owner would actually say, plus event nouns in the body (layoff, acquisition close, policy change). It falls short of anchor 5 because common variations like "town hall announcement", "internal FAQ", or "org change announcement" are absent. Clearly above anchor 3 ('relevant keywords but missing common variations') is not the best fit since most core variations are present.

Distinctiveness Conflict Risk

Clear niche with distinct triggers: the description disambiguates the audience ("the audience is employees (not customers)") and names an explicit role (Head of People Ops, BizOps lead, Internal Communications owner), so it will not fire for external marketing comms or general writing skills. Trigger phrases like "layoff comms" and "manager talking points" are domain-specific with minimal conflict risk, matching anchor 5.