Content
78%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, expert-level instruction body: lean, concrete, and sequenced, with a solid verification checklist. Its main defect is that all three referenced bundle files (demo/index.html, demo/PROMPT.md, REFERENCES.md) are missing from the skill directory, breaking the progressive-disclosure chain, and there is no executable code beyond the config literal.
Suggestions
Ship the referenced bundle files — demo/index.html, demo/PROMPT.md, and REFERENCES.md — or remove/inline their content, since none currently exist and the body's final paragraph directs Claude to read them.
Add one minimal executable snippet (a single requestAnimationFrame loop with delta clamping, an IntersectionObserver visibility gate, and a prefers-reduced-motion early exit) so the core mechanics are copy-paste ready rather than directive-only.
Add brief error-recovery guidance to the Verify section (e.g., what to do when multiple loops survive repeated mounts or when resize causes particle counts to explode) to close the feedback-loop gap in workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative with zero padding — no explanations of concepts Claude already knows ("Never attach a listener per particle", "Use one `requestAnimationFrame` loop for the whole layer", "Start with the least expensive renderer"). Every token adds guidance Claude would not infer on its own. | 5 / 5 |
Actionability | A concrete config literal plus highly specific directives ("cap canvas backing resolution at `min(devicePixelRatio, maxDpr)`", "Set the layer to `pointer-events: none`") make the guidance mostly executable, but the skill stops short of any runnable implementation of the loop, observers, or reduced-motion fallback beyond the config object — minor gaps keep it below fully copy-paste ready. | 4 / 5 |
Workflow Clarity | Sections give a clear ordered workflow (renderer → config → layer → simulation → pausing → accessibility → Verify) and the Verify section acts as an explicit test checklist including "Confirm only one animation loop survives repeated mounts". However, sequencing is partly implicit in heading order and there are no error-recovery feedback loops, matching the 4 anchor (clear sequence, most checkpoints) rather than 5. | 4 / 5 |
Progressive Disclosure | The body is well-organized and its references are clearly signaled with distinct roles ("Use demo/index.html as the working reference", "demo/PROMPT.md to recreate or remix it", "REFERENCES.md as the links-only implementation source list"), but none of those files exist in the bundle — demo/, REFERENCES.md, and any references/ directory are all missing. These dangling references would cause read failures at use time, matching the 3 anchor (structure present, references not reliably usable). | 3 / 5 |
Total | 16 / 20 Passed |