Content
88%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 tightly written, highly actionable instruction-only skill: concrete commands, exact paths, and explicit validation loops for every workflow, with no wasted tokens. The main gaps are the absent example register record format and inline scoring/publisher detail that belongs in the referenced protocol file.
Suggestions
Add a minimal example record (or field list) for src/data/source-acquisitions.json so a 'find' or 'add' capture can be written correctly without consulting the external protocol doc.
Move the band-score arithmetic ('76 unreviewed and 91 once signed off') and the unregistered-publisher list into docs/source-acquisition-protocol.md, keeping only the decision rule inline.
Verify the '../../../docs/source-acquisition-protocol.md' relative link resolves from the skill's installed location, or move the protocol into a references/ file inside the skill bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~80-line body is dense with project-specific rules — the locality ladder, register dispositions, band semantics, publisher registry consequences — and never explains anything Claude already knows; even justifications like 'Fabricated provenance is the worst failure this system can produce, because it looks exactly like real provenance' earn their tokens by calibrating judgment. Every line carries a rule or a consequence, matching the 'every token earns its place' anchor. | 5 / 5 |
Actionability | Guidance is highly concrete: exact commands ('npm run check:source-acquisitions', 'npm run check:source-catalogue'), exact file paths ('src/data/source-acquisitions.json', 'src/lib/source-authority-registry.ts', 'tests/source-catalogue-providers.test.ts'), concrete expected scores ('76 unreviewed and 91 once signed off'), and a specified report table format. It falls short of 5 only because no example register record or its field format is shown inline — the entry schema is left to the protocol doc and the checker. | 4 / 5 |
Workflow Clarity | Each verb has a numbered sequence with an explicit validation checkpoint and a feedback loop — 'Run `npm run check:source-acquisitions` and fix what it names' for find, checks for add, and a state-printing review — plus guidance for blocked paths (unregistered publishers: 'Report it to the owner... and stop'). This matches the 5 anchor's validate → fix → retry pattern applied to batch register operations. | 5 / 5 |
Progressive Disclosure | Good structure: the body is a well-sectioned overview with the full protocol offloaded one level deep to a clearly signaled reference ('Full protocol: docs/source-acquisition-protocol.md') and rules located by path in source files. It falls short of 5 because no bundle files (references/, scripts/, assets/) exist, the protocol link points outside the skill bundle with a fragile '../../../' relative path, and inline detail like band-score arithmetic and the unregistered-publisher list could live in the referenced protocol. | 4 / 5 |
Total | 18 / 20 Passed |