Content
88%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 tightly written, highly actionable orchestrator skill with explicit gates, validation loops, and a well-organized reference structure. The only gap is a few referenced files missing from the bundle.
Suggestions
Add the missing `references/bgm.md` and `sub-agents/frame-worker.md` files (or correct the paths) so the referenced navigation lands.
Consolidate the repeated analyzer-trust caveat (Steps 0, 1, and 2) into one canonical statement referenced from each step to trim tokens.
Verify the `../hyperframes-core` and `../hyperframes-creative` cross-skill paths are resolvable from the install location, since a broken sibling path blocks Step 3 and Step 4.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and assumes competence ("Keep design and motion rules out of this file"), but the analyzer-trust caveat is restated across Steps 0/1/2 and the orchestration framing repeats, adding minor padding. | 4 / 5 |
Actionability | Fully executable: copy-paste bash for every step (init, analyze-beatgrid.py, validate-plan.mjs, assemble-index.mjs, hyperframes lint/validate/inspect/render) with concrete flags and output paths. | 5 / 5 |
Workflow Clarity | Seven sequenced steps each with an explicit **Gate**, a validate-plan.mjs fix-loop ("Fix every ✗... iterate until they approve"), and a Resume table mapping artifacts to re-entry points. | 5 / 5 |
Progressive Disclosure | Clear overview with a one-level-deep reference table and directory layout, but three referenced paths do not exist in this bundle (references/bgm.md, sub-agents/frame-worker.md, and the cited frame-worker link), slightly weakening navigation. | 4 / 5 |
Total | 18 / 20 Passed |