Conciseness

Lean throughout: a two-sentence motivation ('Docs drift when code changes... a stale one leads them astray'), then only operational content — safety boundaries, what to check, what to file. No explanation of concepts Claude already knows and no padding, matching the level-5 anchor where every token earns its place.

Actionability

Gives copy-paste-ready guidance: the issue title template 'Docs: <file> is out of date', a body format with a concrete line-pointer example 'src/games/water-cannon/game.ts:12', the verification command 'npm run check', and exact paths ('src/games/<game-id>/README.md', 'skills/', 'tessl-factory/skills/'). For an instruction-only skill this fully matches the level-5 anchor.

Workflow Clarity

The sequence is clear (read each doc, check claims against code, dedup against open issues, file one issue per stale doc) and key checkpoints are explicit ('Before filing, check the open issues and skip', 'Run commands like `npm run check` if you need to confirm one works', 'Nothing found is a fine result'). Held at 4 rather than 5 because steps are conveyed through section order rather than an explicit sequence, and there is no post-filing verification or feedback loop for this batch write operation.

Progressive Disclosure

A single self-contained file (~46 lines) with no bundle directories and well-organized sections ('Staying safe', 'What to check', 'What to file'). Per the rubric's guideline for skills under 50 lines with no need for external references, this scores 5 on organization alone.

Specificity

Names the domain and several concrete actions — 'Find docs and agent instructions... that no longer match the code, and file one GitHub issue per stale doc' — plus enumerated targets (README, AGENTS.md, game READMEs, skills) and a write boundary ('Files issues only; never changes code or docs'). Scored 4 rather than 5 because the action list stops at two core verbs, leaving minor coverage gaps (e.g., how claims get verified), and clearly exceeds the 1-2-action level 3 anchor.

Completeness

Explicitly answers both questions: the 'what' ('Find docs... that no longer match the code, and file one GitHub issue per stale doc') and the 'when' ('Use when running the doc gardening maintenance loop, or when asked to check whether the README, AGENTS.md, a game's README or a skill is out of date'). The 'Use when' clause with concrete trigger phrases matches the level-5 anchor exactly.

Trigger Term Quality

Covers the natural phrases a user would actually say — 'out of date', 'stale doc', 'doc gardening maintenance loop' — alongside specific file names ('README', 'AGENTS.md', 'a game's README', 'a skill'), giving comprehensive coverage including synonyms. This matches the level-5 anchor better than level 4 because both synonyms (stale / out of date) and concrete file names are present.

Distinctiveness Conflict Risk

A clear niche — code/doc staleness checking plus issue filing in a specific repo ('the carnival') — with the explicit boundary 'Files issues only; never changes code or docs' distinguishing it from doc-editing or general review skills. Minimal conflict risk, matching the level-5 anchor rather than the minor-overlap level-4 anchor.