Content
73%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-engineered orchestration workflow: explicit state routing, a condition-indexed reading table, an eight-stage build sequence with lint/check validation gates, and a completion checklist. Weaknesses are verbosity in the companion-flow and dispatch prose, and one dangling internal reference (sub-agents/frame-worker.md) in an otherwise well-structured bundle.
Suggestions
Cut the companion-flow commentary to directives only — e.g., replace 'Arrive as the director, not the contractor...' with 'Deliver the strongest treatment the brief supports; flag expensive layers (render time, sign-in, billing) as you name them.'
Add or restore `sub-agents/frame-worker.md` so the dispatch step's reference to this skill's own bundle resolves.
Break the stage-1 plan paragraph into a short bulleted list (plan contents, catalog search, storyboard recording) so each rule is scannable instead of one long sentence chain.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with directives and correctly assumes Claude's competence (no explanation of what video editing or timelines are), but passages like "Arrive as the director, not the contractor. A user who chose companion chose involvement and quality; the honest response is the best version you can design..." and the multi-clause catalog-search sentence in stage 1 are taste commentary and run-on prose that could be cut roughly in half. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4. | 3 / 5 |
Actionability | Owned operations are copy-paste ready: `npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video`, `npx hyperframes check`, `node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes <PROJECT_ROOT>`, and `node <SKILL_DIR>/scripts/frame-packets.mjs --project "$PROJECT_DIR" --storyboard ...`. It falls short of 5 because several core operations (clip-range editing contracts, storyboard block format, worker role) are delegated to reference files with no inline minimal example, and placeholders like `$PROJECT_DIR` are used before being defined. | 4 / 5 |
Workflow Clarity | Stages 1–8 give a clear dependency-ordered sequence with explicit validation checkpoints: "Use `npx hyperframes lint` for fast feedback", "For the final gate, run `npx hyperframes check`", a full "## 7. Done" completion checklist, and a first-matching-row state table for project state. This matches the anchor-5 pattern of sequence plus explicit validation and completion criteria. | 5 / 5 |
Progressive Disclosure | Structure is good: a conditions table maps each situation to the exact reference to load, references are clearly signaled and mostly one level deep, and the bundle's own script `scripts/frame-packets.mjs` exists as referenced. Not 5 because the body cites this skill's own `sub-agents/frame-worker.md`, which is not present in the bundle, and the body inlines several long passages (companion flow, dispatch guidance) that read as reference material rather than overview. | 4 / 5 |
Total | 16 / 20 Passed |