Content
82%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 tight, executable reference: complete install/mount/render commands, a fully specified variable table, an explicit runtime contract, and hard-won editing rules stated as constraints rather than explanations. The only deductions are scattered pinned version numbers, a missing post-install verification step, and structure that is solid but not exceptionally split. All listed bundle files check out against the actual assets directory.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and dense with information Claude would not already know (composition id, variable ranges, runtime contract, editing rules) — nothing explains known concepts. Not a 5 because pinned version numbers (hyperframes@0.8.12, three.js 0.181.2, GSAP 3.14.2) are time-sensitive information scattered inline rather than isolated, which the guidelines say penalizes conciseness. | 4 / 5 |
Actionability | Everything is copy-paste executable: the install command 'npx hyperframes add wireframe-portal-title', a complete mount <div> with all data attributes, a full render command with example --variables JSON, and a variable table with types, defaults, and step ranges. Not below 5 because no key execution detail is missing. | 5 / 5 |
Workflow Clarity | The install → mount → render sequence is clearly ordered, with numbered editing rules and a seek-safety contract. Not a 5 because there is no validation checkpoint (e.g. verifying the block mounted or the timeline registered) after install/mount; not 3 because the operations are non-destructive single-purpose renders, so validation gaps are minor rather than missing. | 4 / 5 |
Progressive Disclosure | Structure is good: a Files section accurately listing the bundled assets (the three Geist TTFs and OFL license all exist under assets/fonts/), sections for Install/Variables/Runtime contract/Editing rules, and one-level references with no nesting. Not a 5 because the skill runs slightly over the under-50-line simple-skill threshold and the large 63 KB composition HTML carries all implementation detail in a single inline-referenced file, which is appropriate here but leaves organization gains on the table. | 4 / 5 |
Total | 17 / 20 Passed |