Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured orchestrator skill with strong workflow sequencing, validation checkpoints, and a resume table. It loses points on actionability and progressive disclosure because the central design/build phases delegate to several files that are not present in the bundle, and the body carries some length and a maintainer-only section.
Suggestions
Add the referenced dispatch files to the bundle (agents/director.md, agents/builder.md, agents/finalize.md, categories/<id>/module.md, phases/source/guide.md, catalog-map.md) or inline a minimal executable version of each phase so the build path is self-contained and copy-paste ready.
Tighten the body by collapsing the overlap between the opening dispatch note and the Categories section, and consider moving the trailing 'Design notes (maintainers — execution does not read this)' out of SKILL.md into a separate maintainer reference.
Replace the 'illustrative' Step 2 snippet with the actual resolve.mjs command (or ship phases/source/resolve.mjs) so the source step is executable rather than a pointer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and skill-specific (phase table, category tables, resume table) rather than padded with concepts Claude knows, but it is lengthy with some overlap between the top dispatch note and the Categories section, plus a trailing 'Design notes (maintainers)' block — matching 'mostly efficient but could be tightened', not the fully lean top anchor. | 2 / 3 |
Actionability | Real executable commands appear where present ('(cd "$PROJECT_DIR" && npx hyperframes init ... --example=blank', render/lint/inspect), but the central design/build steps delegate to files absent from the bundle (agents/director.md, agents/builder.md, categories/<id>/module.md) and Step 2 is labeled 'illustrative — see phases/source/guide.md', matching 'some concrete guidance but incomplete / missing key details'. | 2 / 3 |
Workflow Clarity | Steps 0–6 are clearly sequenced with explicit checkpoints ('[ -s "$PROJECT_DIR/shot-plan.json" ] && echo ok || echo missing', lint/inspect → repair subagent with a re-render feedback loop) and a Resume table mapping state to continue-from, matching the 'clear sequence with explicit validation steps; feedback loops' anchor. | 3 / 3 |
Progressive Disclosure | The three real references (motion-vocabulary.md, shot-plan-ir.md, builder-contract.md) are well-signaled and one-level-deep, but many other references in the body (agents/director.md, agents/builder.md, agents/finalize.md, categories/<id>/module.md, phases/source/guide.md, catalog-map.md) are not present in the bundle, so navigation is only partially verifiable — matching 'some structure but could be better organized' rather than a fully clean overview. | 2 / 3 |
Total | 9 / 12 Passed |