Content
92%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 highly actionable, well-gated companion skill: exact API surface, precise public-vs-internal naming rules, a cost-aware verification loop with an ffmpeg command, and cleanly split one-level-deep references. Its only weakness is mild repetition of the render-cost message in the verification section.
Suggestions
State the render-cost caution once in the Verifying the animation section and drop its restatements (e.g. "so make each render count" in the intro line, "make each one count instead of re-exporting after each small change", and "Higher just bloats the render") to tighten conciseness.
Trim justification sentences like "Otherwise you'll burn calls and confuse the user with repeated identical failures" to the bare rule ("Do not retry; tell the user motion isn't enabled and stop") since the reason is evident from the error.
Consider collapsing the numbered "Plan before rendering" steps' parenthetical asides (e.g. the 1x/10x/4096px clamp detail) into the reference docs to reduce inline token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence (no explanation of what Figma or animation is), but the render-cost caution is repeated across several paragraphs of the verification section ("make each render count" appears in multiple forms) and a couple of justification sentences could be trimmed — efficient with minor instances of over-explanation, the 4 anchor. | 4 / 5 |
Actionability | Fully executable guidance: exact API names and signatures, exact public enum values (EASE_IN_AND_OUT vs EASE_IN_OUT), concrete export_video parameters (constraint: { type: 'WIDTH', value: 320 }, quality: "low", fps: 5), and a copy-paste ffmpeg frame-extraction command — matching the fully-executable 5 anchor. | 5 / 5 |
Workflow Clarity | Clear gated sequence (feature-flag bail-out on a named error), a well-ordered verification workflow with an explicit feedback loop (export → poll → extract frames → read all → batch fixes → re-render until right), and a pre-flight checklist — the 5 anchor with validation checkpoints and error-recovery loops. | 5 / 5 |
Progressive Disclosure | The body is an overview (~65 lines) with a well-signaled "when to load / what it covers" table pointing to two real one-level-deep reference files; the anchor link used (motion-patterns.md#animatable-fields) resolves to an actual heading, and the companion-skill cross-link is explicit — matching the 5 anchor. | 5 / 5 |
Total | 19 / 20 Passed |