Content
71%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 exceptionally actionable — every workflow step is a copy-paste command, and the runtime contract and editing rules are precise and non-obvious. Its weaknesses are structural: the 216-row variables table is a monolith that belongs in a separate reference file (and its cell values contain unescaped pipes that break the markdown table rendering), and the headline composition file listed in the Files section is missing from the bundle.
Suggestions
Move the 216-row variable table to a reference file (e.g. `references/variables.md`) and keep a short categorized summary in SKILL.md (e.g. "Material, Break, Flight, Return, Light, Post groups — full table in references/variables.md").
Escape or replace the literal pipe characters in cell values (e.g. `"Hard to|break."`, enum lists like `physical|directed|hybrid`) — they currently split cells and break the markdown table rendering.
Add a post-install verification step (e.g. confirm `compositions/frost-sequence-camera-orbit/frost-sequence-camera-orbit.html` exists) and clarify why the primary HTML file is absent from the skill bundle, or include it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The prose sections are lean with no concept over-explanation, but the inline 216-row variable table consumes roughly three quarters of the body's tokens and loads on every skill invocation even when customization is not the task; the opening paragraph also restates the frontmatter description. Anchor 3 ("could be tightened") fits better than 4, and nothing pads or explains known concepts, so it is not a 2. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready guidance throughout: `npx hyperframes add frost-sequence-camera-orbit`, a complete data-composition-* mount snippet, and `npx --yes hyperframes@0.8.12 render ... --variables '{"headline1":"Hard to|break."}'` with a concrete customization example, plus exact runtime APIs (`window.__hyperframes.getVariables()`, `window.__timelines["frost-sequence-rig"]`). The common cases — install, embed, custom render — are all covered. | 5 / 5 |
Workflow Clarity | Files → Install → mount → render → editing rules is a clear, unambiguous sequence with exact commands at each step. It falls short of anchor 5 because there are no validation checkpoints or error-recovery guidance (e.g. verifying installed files or a rendered test frame), though the non-destructive nature means the 3-cap does not apply. | 4 / 5 |
Progressive Disclosure | Sections are clearly organized and the bundle is genuinely one level deep (assets/ with 16 real files matching the listing), but ~220 lines of variable reference are inlined in SKILL.md instead of split into an on-demand reference file, and the primary listed file `frost-sequence-camera-orbit.html` (131 KB) is absent from the actual bundle. This matches anchor 3 — real structure present, but content that should be separate is inline. | 3 / 5 |
Total | 15 / 20 Passed |