Content
93%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 an exemplar of dense, executable skill writing: a complete JSON island example, exact commands, hard failure modes (MP4 truncation, click-swallowing invisible layers) and a validation loop, with bulk edge-case detail correctly pushed to a single well-signaled reference. The only gap is that the workflow is organized by topic rather than as an explicit ordered sequence with error-recovery steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every bullet carries non-obvious, tool-specific facts (fragments use the absolute timeline clock and "Navigation seeks, it never plays"; hidden stacked slides need all three of opacity/visibility/pointer-events; "render keeps only the first scene and truncates silently"), assumes the /hyperframes contract without re-explaining it, and never pads with concepts Claude already knows. Not 4: there is no over-explanation to trim — even the Meet/Zoom screen-sharing lines are practical, unknown detail. | 5 / 5 |
Actionability | Provides a copy-paste-ready JSON island example plus exact commands with flags (`npx hyperframes catalog --query "..." --json`, `npx hyperframes check --json`, `npx hyperframes present <project-dir>`, `snapshot --at`), concrete attribute names and the exact hand-off line to say. Not 4: the common cases are covered end-to-end with nothing left as pseudocode or vague direction. | 5 / 5 |
Workflow Clarity | An explicit validation checkpoint exists ("Run `npx hyperframes check --json` until it is clean", with what the check verifies) and the sections imply a build → check → present → hand-off arc. Not 5: the sequence is thematic rather than explicitly ordered (e.g., when to search the catalog relative to hand-building is only implied), and there is no error-recovery guidance for check failures. | 4 / 5 |
Progressive Disclosure | A ~60-line overview keeps only decision-relevant rules inline and splits the 1000-line edge case ("A deck opened from the bare player bundle without `present` needs workarounds: `references/standalone-harness.md`") into a clearly signaled, one-level-deep, verified reference with no nested .md links. Not 4: nothing that belongs in a reference is inlined and navigation is unambiguous. | 5 / 5 |
Total | 19 / 20 Passed |