Content
78%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.
The body is an efficient, clearly sequenced planning workflow with explicit gates and go/no-go criteria, which is impressive for an instruction-only skill. Its main structural flaw is that the two bundle reference files (plan template, review checklist) are completely unlinked, so the model must rediscover them and the inline summaries duplicate bundle content instead of pointing to it.
Suggestions
Link the bundle files where their content is summarized: in step 2, "Create plan.md following references/plan-template.md" and in step 6, "Run each pass using references/plan-review-checklist.md".
Add a brief note on what invoking `pickup`, `oracle`, and `handoff` should produce (or where their definitions live) so the mandatory passes are self-contained.
State the failure path for the commit gate, e.g. "If any GO condition fails, return to the relevant step (5 or 6) and iterate — do not hand off on a NO-GO."
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive throughout — terse bullet instructions like "Read brief → breadboard → risk register → spikes", "Record concrete file paths", and a five-line commit gate with no concept explanations Claude already knows and no padding. Every line instructs; it matches the 'every token earns its place' anchor and is clearly above anchor 4, where minor over-explanation would remain. | 5 / 5 |
Actionability | Mostly executable guidance for an instruction-only skill: named input files (brief.md, breadboard-pack.md, risk-register.md), an enumerated plan.md skeleton, explicit external-research conditions ("security/auth, payments, privacy, external APIs, migrations"), a five-condition GO gate, and a handoff content list. It falls short of anchor 5 because key mechanics are delegated to undefined invocations ("invoke `pickup`", "invoke `oracle`", "invoke `handoff`") with no pointers, and review passes like "Simplicity, risk, ops/release" give no pass/fail criteria in the body; it is above anchor 3 because the guidance is concrete and specific rather than pseudocode-level. | 4 / 5 |
Workflow Clarity | A clearly numbered 0-8 sequence with routing on bad inputs ("If perimeter or top risks are missing: route back to wf-shape"), conditional branches, a commit gate, a Verification section, and an explicit Go/No-Go with a concrete NO-GO condition. It is below anchor 5 because the review passes in step 6 lack stated validation criteria in the body (the checklist exists only as an unreferenced file) and no explicit fix-and-retry loop is described for a failed commit gate; it is above anchor 3 because checkpoints (commit gate, GO/NO-GO, oracle pass) are explicit rather than implicit. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned (Purpose, Inputs, Outputs, Steps, Verification, Go/No-Go) but never links to either bundle file: references/plan-template.md and references/plan-review-checklist.md are not mentioned anywhere, while their content is re-summarized inline (the plan.md skeleton in step 2 and the review dimensions in step 6). This matches the anchor 'references present but not clearly signaled; content that should be separate is inline' — it is above anchor 2 because the inlined content is a compressed overview rather than the full files dumped into the body, and below anchor 4 because not a single reference path is surfaced. | 3 / 5 |
Total | 16 / 20 Passed |