Content
55%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 skill has excellent workflow discipline — a clear phased chain with real validation gates and per-recipe VERIFY criteria — but it ships without any of the reference files its guidance depends on, and the body duplicates its own chain, handoffs, and thresholds across four sections. As delivered it is a well-designed index to a bundle that is not there.
Suggestions
Ship the referenced bundle files (reference/blueprint-method.md, recipe-design.md, workflow-design.md, delegation-handoffs.md, validation-checklist.md, autorun-schema.md, and the _common/*.md files) or inline their essential content — currently every 'Read When' pointer is dangling.
Consolidate the phase-chain documentation: keep the canonical Workflow table and have the Recipes, Operating Flows, and Subcommand Dispatch sections reference it instead of restating it, removing roughly a third of the body.
Collapse the triple-duplicated collaboration material (HTML comment block, ASCII diagram, and handoff table) into the single Collaboration table and move per-agent payload details to reference/delegation-handoffs.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably padded through duplication: the SURVEY→MAP→DESIGN→DELEGATE→VERIFY chain appears four times (Workflow table, Operating Flows, Recipes table, Subcommand Dispatch), the delegation handoffs are listed three times (HTML comment block, ASCII collaboration diagram, Collaboration table), and the Critical Thresholds table restates Core Contract items. It avoids explaining concepts Claude already knows, which keeps it above level 1, but the redundancy is well beyond 'minor instances that could be trimmed'. | 2 / 5 |
Actionability | There is genuinely concrete guidance — exact thresholds ('≤ 5 sequential phases', 'overlap under 30%', '≤ 7 specialists per orchestrator'), a dispatch rule for the first input token, and a copyable NEXUS_HANDOFF schema — but the actionable detail for each phase (blueprint method, recipe patterns, topology selection, delegation payloads, the 14-item checklist) lives entirely in `reference/*.md` and `_common/*.md` files that are absent from the bundle, leaving key steps unexecutable as shipped. That matches 'some concrete guidance but incomplete; missing key details' rather than level 4. | 3 / 5 |
Workflow Clarity | The phase chain is explicit and consistently applied, each phase has a stated purpose and a named reference to load on entry, each recipe has its own **VERIFY** gate in addition to the universal discipline, and the 14-item checklist blocks delivery until it passes — a textbook validation checkpoint with feedback-loop semantics ('Delivery is blocked until it passes'). | 5 / 5 |
Progressive Disclosure | The structure is well designed — a Reference Map table with 'Read This When' conditions per file, references one level deep, clearly signaled per phase — but none of the referenced files (7 `reference/*.md` and 4 `_common/*.md`) exist in the bundle, so navigation leads nowhere, and substantial content that belongs in those files (per-recipe behavior notes, the collaboration handoff tables, threshold rationale) is inlined in the ~295-line body instead. This sits between 'references present but not clearly signaled' (they are signaled) and 'most content appropriately placed' (it is not, given the missing bundle), so 3 rather than 4. | 3 / 5 |
Total | 13 / 20 Passed |