Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly usable overview: the decision tree, output template, failure handling, and anti-patterns are all directly actionable, and the structure points clearly to deeper material. Remaining gaps are small — a redundant Contract section, an underspecified cross-link step, and references that point outside the skill bundle itself.
Suggestions
Trim or merge the Contract section — its three bullets restate the decision protocol and preview the Anti-Patterns section.
Make the cross-link phase concrete: which related pages or directories to link from, and the link format to use.
Promote "check if a page already exists" from an Anti-Pattern into an explicit phase/validation step in the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~45-line body is lean and assumes competence: a concrete decision tree ("About a person → `people/{name-slug}.md`"), an output template, failure handling, and anti-patterns, with no explanation of concepts Claude already knows. Minor trimmable redundancy keeps it at anchor 4 rather than 5: the Contract section ("Every new page is filed by primary subject (not format, not source)") restates the decision protocol and previews the Anti-Patterns section. Not anchor 3, since the redundancy is a single summary section rather than pervasive padding. | 4 / 5 |
Actionability | Concrete, executable guidance throughout: exact directory patterns in the decision tree, a copy-paste output template ("File this at `{type}/{slug}.md` because the primary subject is {reason}."), and specific failure handling ("`get_page` returns `page_not_found` ... confirm the slug with the user before choosing a directory"). Per the scoring notes, absence of code is not penalized in an instruction-only skill. Anchor 4 rather than 5 because "Cross-link. Link from related directories." is underspecified — no indication of which pages to link from or in what format. | 4 / 5 |
Workflow Clarity | Four clearly numbered phases with an explicit checkpoint ("Check notability. See `skills/conventions/quality.md` notability gate") and an error-recovery section covering fallbacks (fall back to `skills/_brain-filing-rules.md`; confirm the slug on `page_not_found`). Anchor 4 rather than 5 because the "check if a page already exists" validation appears only in Anti-Patterns rather than as a workflow step, and the notability gate's criteria are deferred to an external file. The destructive/batch cap does not apply — the skill is advisory (`mutating: false`). | 4 / 5 |
Progressive Disclosure | The body is a genuine overview with clearly signaled, one-level-deep references — "> **Full filing rules:** See `skills/_brain-filing-rules.md`" at the top, plus `skills/conventions/quality.md` and `../conventions/agent-operator-protocol.md` — and well-organized sections (Contract, Phases, Output Format, When it fails, Anti-Patterns). Anchor 4 rather than 5 because no bundle directories exist to verify the referenced files and the references are repo-relative code-formatted paths rather than links within the skill bundle, a minor navigation/organization gap. | 4 / 5 |
Total | 16 / 20 Passed |