Conciseness

The ~23-line body is lean with no explanations of concepts Claude already knows; every clause is operational (e.g., "because pnpm hands its arguments to `sh` inside double quotes, so each backticked span or `$` in the text runs as a command" is a load-bearing safety rationale, not padding). It matches anchor 5 (every token earns its place) rather than anchor 4, since trimming any clause would lose actionable content.

Actionability

Steps give exact executable commands ("node tooling/scripts/notify.mjs send --to <login or dev> \"$(cat <file>)\"", "gh issue view <N> --repo <owner/repo> --json title -q .title", "node .agents/pstack/writing-check.mjs <file>"), an exact link format, and handling for every common case including edge cases (off-team recipient, `skipped:` output, 2000-character split, unpushed commit hashes). Per the rubric's code-vs-instruction note, this instruction-only skill's guidance is fully concrete, matching anchor 5.

Workflow Clarity

A clear five-step sequence (pick recipient, draft, validate, send, report) with an explicit validate-and-fix feedback loop in step 3 ("Run `node .agents/pstack/writing-check.mjs <file>` and fix each line it prints") before the send, plus failure handling in step 1 ("stop and say so") and step 5 ("When the command prints `skipped:`, say so"). This matches anchor 5's explicit validation with error-recovery feedback loops; the destructive/batch cap does not apply since this is a single non-destructive send with validation present.

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no bundle files; per the rubric's simple-skills note it qualifies for a 5 with well-organized sections, which the numbered steps provide. Detail is correctly delegated one level deep to clearly signaled project files (`.agents/pstack/rules/writing.md`, `.agents/pstack.json`, `tooling/scripts/notify.mjs`) with only the key rules inlined.

Specificity

"Send a Discord message as plate-bot to a teammate or the dev role in the team channel, in the team's house style" names one core action with concrete parameters (sender identity, recipients, channel, style), plus enumerated variants (telling, pinging, answering a pasted message, retest notices). This lists several specific actions with minor gaps (anchor 4), not the comprehensive multi-action coverage of anchor 5, and well above anchor 3's bare 1-2 actions.

Completeness

The what is explicit ("Send a Discord message as plate-bot to a teammate or the dev role in the team channel, in the team's house style") and the when is an explicit "Use for..." clause with concrete triggers (/notify, telling/pinging, answering a pasted message, playbook-mandated sends, retest notices). This clearly matches anchor 5's requirement of both what and when with concrete trigger phrases, exceeding anchor 4 where the when is only present but less specific.

Trigger Term Quality

"Use for /notify, for telling or pinging a teammate, for answering a teammate's pasted Discord message, and for every team message a playbook or rule has a session send, such as a retest notice" covers the natural trigger phrases for this niche comprehensively, including synonyms (telling/pinging, message/notice) and a catch-all clause. Anchor 4 would require noticeably missing natural terms, and few remain in this niche.

Distinctiveness Conflict Risk

The combination of "Discord message as plate-bot", "team channel", and "retest notice" carves out a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5 rather than anchor 4's minor overlap with closely related skills.