Content
75%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 skill body is a tight, well-structured reference of practical motion defaults that largely assumes Claude's competence and avoids over-explaining basics. Its main weakness is that the promised code recipe is described but never delivered, slightly undercutting actionability and workflow completeness.
Suggestions
Include at least one concrete, copy-paste-ready code recipe (CSS transition and a GSAP/Framer Motion timeline) so the 'Output format' recipe step is actionable, not just named.
Add an explicit verification checkpoint to the workflow, e.g., 'Confirm prefers-reduced-motion fallback was applied and no width/height/top/left properties are animated,' to close the workflow-clarity loop.
Trim light framing prose (e.g., 'Think in primitives you can reuse everywhere', 'Not more animation. Better animation') to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and well-organized with practical defaults rather than explanations of concepts Claude already knows, though a few framing lines like 'Think in primitives you can reuse everywhere' and the opening 'Not more animation. Better animation' add light padding that could be trimmed. | 4 / 5 |
Actionability | Provides concrete, copy-ready numbers (e.g., 'Opacity: 0 -> 1', 'Y: 12-24px -> 0', '120-200ms', 'ease-out') and explicit property guidance (transform/opacity over width/height), but the promised 'small code recipe' in the output format is never shown and implementation guidance stays library-named rather than executable. | 4 / 5 |
Workflow Clarity | The 'Output format' section sequences the deliverables into a clear 5-step plan (goals -> tokens -> choreography -> implementation -> recipe) and the 'What to ask the user' section acts as a discovery checkpoint, but there are no explicit validation or verification checkpoints after producing the motion plan. | 4 / 5 |
Progressive Disclosure | Content is organized into clearly headed one-level sections (primitives, defaults, choreography, performance, accessibility, implementation) with no bundle files present, keeping everything appropriately in a single well-structured overview; minor gaps are just that some dense token/easing tables could optionally live in a reference file. | 4 / 5 |
Total | 16 / 20 Passed |