Conciseness

The body is dense and lean overall, and the smell/why/fix table earns every token, but the PRD exception is stated three times ('History, corrections, and discovery narratives belong in PRDs', the 'This is a different rule from prd-writing' paragraph, and 'This does not apply to PRDs'), which is trimmable repetition.

Actionability

The sweep commands are copy-paste ready ('grep -rniE "as of 202|caught in review|..."' and 'grep -rn "—"') and the smell table pairs each violation pattern with a concrete fix, covering the common cases for an instruction-only skill.

Workflow Clarity

A clear sequence is present (apply rules, run the sweep, 'Read every hit in context', fix violations, sync the three trees) with the sweep as an explicit validation checkpoint, but there is no re-run/feedback loop after fixes and 'scripts/check_skill_pairs.py' is described rather than given as a command to run.

Progressive Disclosure

A well-sectioned single file with no unnecessary external references, which is appropriate at this size; however, the bullet 'Research docs don't need cross-tree sync ... so this section doesn't apply to them' sits inside the 'Also applies to: research/audit docs' section, contradicting the section it is placed in.

Specificity

'Covers the two standing rules for living-reference prose - state current behavior only, and prefer plain, short wording - plus the grep sweep to run before calling a doc clean' lists several concrete actions, but it omits the body's Rule 3 (em-dash ban) and the cross-tree sync guidance, leaving minor coverage gaps.

Completeness

Both halves are explicit: what ('Covers the two standing rules ... plus the grep sweep') and when ('Read before writing or editing any SKILL.md, or any research/audit doc in .gemini/internal-docs/research/'); the when is framed as an instruction rather than a natural 'use when' trigger phrase, keeping it just below a 5.

Trigger Term Quality

Natural phrases like 'SKILL.md', 'writing or editing', 'research/audit doc', and 'calling a doc clean' match what a user would actually say, though common variations such as plain 'skill' or 'documentation' are missing.

Distinctiveness Conflict Risk

A clear niche (hygiene of living-reference prose in named repo paths) with an explicit carve-out - 'PRDs are the deliberate exception (they keep a correction trail)' - distinguishing it from prd-writing, so conflict risk is minimal.