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.
The body is a tightly sequenced orchestrator workflow with executable commands, explicit gates, and validation feedback loops, supported by a clean one-level-deep reference and script bundle. Its only weakness is mild verbosity in a few framing passages.
Suggestions
Tighten the repeated orchestrator/framing sentences (e.g. the 'You are the orchestrator' lines that recur across the intro and Step 0) to recover tokens without losing the gate logic.
Consider collapsing the sign-in status rationale in Step 0 into a shorter rule plus a pointer, since the exit-code contract detail is borderline over-explained for an orchestrator skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence with no basic-concept padding, but a few passages repeat the orchestrator framing and gate rationale that could be trimmed without losing clarity. | 4 / 5 |
Actionability | Every step ships copy-paste-ready commands (e.g. `npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=product-launch-video`, `node <SKILL_DIR>/scripts/build-frame.mjs --preset <name> --hyperframes .`) with flags explained, covering the common cases fully. | 5 / 5 |
Workflow Clarity | A clear Step 0→6 sequence with an explicit **Gate:** after every step, hard-stop validation on capture failure, and feedback loops for lint/check/snapshot ('fix it yourself… then rerun the failed check'), satisfying the destructive/batch validation bar. | 5 / 5 |
Progressive Disclosure | Overview body points to one-level-deep, well-signaled references (references/story-design.md, visual-design.md, motion-language.md, cut-catalog.md) and scripts, with a Quick Reference table mapping each read to its step; all referenced bundle files exist on disk. | 5 / 5 |
Total | 19 / 20 Passed |