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.
A well-structured orchestration skill: lean, directive prose with an explicit phased workflow, genuine feedback loops, and clean one-level-deep reference files verified to exist and carry real content. The only gap is reliance on out-of-bundle sibling skills (how, arena, interrogate, principle skills) for the mechanics of grounding and multi-model synthesis.
Suggestions
Bundle or briefly summarize the contract with the **how** and **arena** skills (expected inputs/outputs of grounding artifacts and the arena task format) so Phase A and Phase B are executable from the skill alone.
Consider linking the other referenced skills (arena, how, why, interrogate) the way design-red-flags.md is linked, so their existence and location are verifiable from the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive ('Design it twice.', 'Naming a file isn't grounding.', 'Subtract before adding') with no explanations of concepts Claude already knows; every rationale sentence (interface depth, scrap tells) is load-bearing judgment guidance rather than padding. | 5 / 5 |
Actionability | Directives are concrete where it counts (explicit fallback runner names 'claude-opus-5-5-xhigh' and 'grok-4.7-xhigh-fast', pass references/runner-prompt.md, screen against references/design-red-flags.md, an explicit scrap-tells checklist), but Phase A and Phase B execution depends on out-of-bundle skills (**how**, **arena**) whose mechanics are neither bundled nor summarized, leaving minor gaps. | 4 / 5 |
Workflow Clarity | The sequence is explicit (todolist with one entry per phase, Phases A-E) with real validation checkpoints (red-flag screening before synthesis, Phase C opt-in sign-off, Phase D deviations surfaced) and error-recovery feedback loops (human pushback treated as Phase A evidence triggering re-ground and re-run; scrap criteria looping back to Phase B). | 5 / 5 |
Progressive Disclosure | The body is an overview-length orchestration layer; all three bundle files exist, are substantive, and are clearly signaled as one-level-deep references (linked references/design-red-flags.md, references/rationale-template.md, references/runner-prompt.md), each loaded only at the phase where it is needed. | 5 / 5 |
Total | 19 / 20 Passed |