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.
A well-organized, token-efficient index skill with concrete routing and a clear composition/escalation workflow. Its main weakness is that the routing table points to a large tree of files not present in the provided bundle.
Suggestions
Bundle the referenced index and adapter files (rules-index.md, blueprints-index.md, transitions/, techniques.md, adapters/*.md) so the routing table resolves to real files, or mark which references are loaded on-demand from elsewhere.
Trim the parenthetical re-list of core's non-negotiable rules in the Critical Constraints section, since the body already says 'Don't restate those here'.
Add one tiny inline composition snippet (e.g. a 3-line paused GSAP timeline) so the default workflow is copy-paste executable rather than purely navigational.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean routing table and tight constraint list with no padding; it does not explain what GSAP/Lottie/Three.js are and explicitly defers core rules to 'hyperframes-core' rather than restating them. Every token earns its place, though the parenthetical core-rules list in Critical Constraints is borderline padding. | 5 / 5 |
Actionability | Concrete file paths, an exact script invocation with arguments, and specific forbidden properties ('never derive positions from getBoundingClientRect() at tween time') give mostly executable guidance; minor gaps because it is navigational with no inline copy-paste recipe. | 4 / 5 |
Workflow Clarity | Clear sequence — default to composing atomic rules, escalate to a blueprint only when stated conditions hold, then route via the table — with a well-formed script usage block; no destructive/batch operations requiring validation checkpoints, so the missing feedback loop is not penalized. | 4 / 5 |
Progressive Disclosure | Excellent one-level-deep structure with a signaling routing table, but many referenced paths (rules-index.md, blueprints/, transitions/, techniques.md, adapters/*.md) are absent from the actual bundle, which only contains the two scripts files — a real organization gap versus the level-5 'appropriately split' anchor. | 4 / 5 |
Total | 17 / 20 Passed |