Content
73%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 well-structured operational contract with excellent gated workflows and concrete decision rules. The main costs are token redundancy (routing stated four times plus a duplicative hidden comment block) and a reference architecture whose target files are not present in the bundle.
Suggestions
Consolidate Trigger Guidance, Subcommand Dispatch, and Output Routing into a single routing table; each currently restates the same signal-to-recipe mapping with different columns.
Remove or drastically shrink the hidden CAPABILITIES_SUMMARY / COLLABORATION_PATTERNS / BIDIRECTIONAL_PARTNERS comment block — it restates the visible Core Contract, Collaboration, and Recipes sections and consumes ~35 lines of context on every load.
Ship the referenced files (reference/intake-checklist.md, reference/supply-chain-malware-*.md, _common/SECURITY.md, etc.) with the skill or inline the few that are load-bearing, since the body's read-triggers currently point at paths absent from the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids concept-teaching, but routing/trigger information is repeated four ways (Trigger Guidance, Recipes, Subcommand Dispatch, Output Routing) and the hidden CAPABILITIES_SUMMARY/COLLABORATION HTML comment (~35 lines) duplicates body sections, so it is mostly efficient but clearly could be tightened — not merely minor trimmings. | 3 / 5 |
Actionability | Concrete, executable decision guidance throughout: exact codepoint ranges (U+E0000–U+E007F), exact credential paths (~/.ssh, ~/.aws, ~/.netrc), quantified rejection gates (< 50 downloads, < 30 days, Levenshtein-2), and named registry endpoints; however the actual scan/verification procedures live entirely in reference files not present in the bundle, leaving minor gaps in executable detail. | 4 / 5 |
Workflow Clarity | Both workflows are explicit phase tables with per-phase gates and feedback loops ("eradicate refuses SUSPECTED", "rotate refuses until the verify-clean gate passes", "verify clean with a second scan", binary checklist per item), which matches the anchor for clear sequencing with explicit validation and error-recovery checkpoints. | 5 / 5 |
Progressive Disclosure | The design is strong — one-level-deep references, read-trigger columns, and full-index pointers (reference/recipes-index.md, reference/reference-index.md) — but no reference/, _common/, or other bundle files ship alongside SKILL.md, so every referenced path is unverifiable from the bundle and cannot earn full marks. | 4 / 5 |
Total | 16 / 20 Passed |