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.
High-quality guidance content: concrete, executable Motion/Vaul code with specific numeric values, real-world bug anecdotes that justify each rule, and a clear decision framework from build-vs-buy through ship checklist to debugging. The main gaps are minor — a few metaphorical asides that could be trimmed and implicit rather than explicit validation checkpoints.
Suggestions
Trim the similes and rationale narration (e.g., "like dragging something through syrup", "like throwing a ball at a wall") to pure imperative rules to tighten conciseness.
Convert the touch checklist and 'When it still feels wrong' section into an explicit ordered ship sequence with a validate→fix→retest loop (e.g., test on real phone → if stutter, re-check track-phase rules → retest) to strengthen workflow clarity.
Consider moving the library-specific Motion drag-props API detail and the Vaul CSS override snippets into a short reference file to improve progressive disclosure and keep SKILL.md as the overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is information-dense with non-obvious knowledge (the Vaul CSS-variable recalculation bug, Sonner's keyframe restart issue, bounce scaling inversely with element size), but includes metaphorical asides like "like dragging something through syrup" and "like throwing a ball at a wall" plus rationale narration that could be trimmed. It sits above the 3 anchor (mostly efficient) but not every token strictly earns its place as the 5 anchor demands. | 4 / 5 |
Actionability | Guidance is fully executable and copy-paste ready: the motion.div example with drag="y", dragConstraints, dragElastic={0.2}, and onDragEnd reading info.offset/info.velocity; exact Vaul CSS overrides with cubic-bezier(0.32, 0.72, 0, 1) at 500ms/200ms; and hard numbers throughout (40–50% dismiss threshold, velocity > 500, 44×44px hit targets, touch-action: pan-x, data-vaul-no-drag). Specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | There is a clear arc — build-vs-library decision, the two-phase track/release model with per-phase rules, the "Run through this for every gesture you ship" checklist, and the "When it still feels wrong" recovery path — so most checkpoints are present. It misses the 5 anchor because validation is implicit (a checklist and a debug section) rather than an explicit validate→fix→retest feedback loop with sequenced steps. | 4 / 5 |
Progressive Disclosure | A single well-organized file with clear, navigable section headers and appropriately self-contained content; cross-references to other skills (pick-ui-library, animation-performance) are clearly signaled. It does not reach the 5 anchor because there are no one-level-deep reference files and the ~100-line body exceeds the under-50-lines simple-skill exception — the Motion drag-props and Vaul-specific sections could plausibly live in reference files. | 4 / 5 |
Total | 17 / 20 Passed |