Content
92%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.
An exceptionally well-crafted body: lean and free of known-concept explanation, rich in concrete commands and named primitives, and structured as a five-step workflow with explicit validation checkpoints, escalation rules, and a failure fallback. The only notable gap is the unexplained ASD-STE100 requirement, which is only partially actionable without the spec or a pointer to it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and telegraphic with essentially no explanation of concepts Claude already knows — it uses Mermaid, Vega-Lite, git worktrees, and file: script restrictions without elaboration — and every line prescribes ("Bright fills on white, by meaning", "A mark on each part of the claim, and on nothing else"). Matches the lean, every-token-earns-its-place anchor; the version notes in Gotchas/Requirements each teach a distinct non-obvious failure mode rather than padding. | 5 / 5 |
Actionability | Concrete commands (`gh-attach shot ... frame.html ... .png`, `git fetch origin <base> && git worktree add ...`, `gh pr view --json baseRefName -q .baseRefName`), an HTML skeleton, and named CSS classes (`.panel pair`, `side before`, `mark`, `kicker`) make the workflow executable. Not 5 because "Words in ASD-STE100 Simplified Technical English" invokes a proprietary standard with no rules or pointer, and `<skill-dir>` resolution is left implicit; well above 3 since the core path is copy-paste ready modulo placeholders. | 4 / 5 |
Workflow Clarity | Five sequenced steps with a "Done when" exit criterion for the brief, an explicit pass/fail checklist in step 4 ("Proves the claim", "Makes sense", "The headline reads clearly"), feedback loops ("fix it at the level it lives at and render again", "When the same shape fails twice, switch shape"), and a defined fallback when no shape can prove the claim. Matches the explicit-validation-with-error-recovery anchor exactly. | 5 / 5 |
Progressive Disclosure | A routing table maps each claim type to one of four clearly signaled, one-level-deep reference files ([screenshots.md], [diagrams.md], [charts.md], [freeform.md]) plus frame.css and render.js, keeping the body a navigable overview of the method. Note: no bundle files were present in the review directory to verify the referenced files exist, so this is scored on the reference structure as written; that structure matches the anchor's clear-overview, well-split, easy-navigation pattern. | 5 / 5 |
Total | 19 / 20 Passed |