Content
77%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 content is well-structured: a clear 5-step workflow with explicit validation and feedback loops, strong actionability via concrete tool calls and field semantics, and exemplary progressive disclosure to six real reference files. The main weakness is conciseness — several rules are restated across Step 3, Critical Rules, and the interleaved-transforms section, adding length without new information.
Suggestions
Consolidate the exact-id-over-fallbackNodeId rule into a single canonical statement; it is currently explained in Step 3, Critical Rule 1's framing, and the componentized-child-motion bullet.
Tighten the interleaved-transforms subsection by folding the duplicate 'keep layout transforms separate from Motion transforms' guidance (Step 3 bullet) into the interleaved-transforms list so each rule appears once.
Move some of the denser Step 3 edge cases (display:contents wrappers, componentized-child matching) into gotchas.md and keep SKILL.md to the core merge rule plus a one-line pointer, to cut token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and avoids explaining basics Claude knows, but it is long (≈140 lines) with several paragraphs that restate the same rule multiple ways (e.g. exact-id-over-fallbackNodeId explained in Step 3, Critical Rules, and interleaved-transforms), so it is mostly efficient but could be tightened. | 3 / 5 |
Actionability | Gives concrete tool invocations (`get_motion_context(fileKey=..., nodeId=..., recursive=true)`), specific field semantics, and explicit code patterns (transformTemplate composition, offset transforms), but motion.dev/CSS snippets themselves are referenced rather than shown inline, leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear 5-step Required Workflow with an explicit validation step (Step 5: validate one animation end-to-end before batching), feedback-loop language ('reload, observe, iterate'), and a Critical Rules checklist covering failure recovery for a batch/destructive-prone task. | 5 / 5 |
Progressive Disclosure | Overview body stays focused on the workflow while six well-signaled, one-level-deep reference files (all present in references/) are loaded on demand with explicit inline 'Load ... before continuing' cues, giving easy navigation with no nested-reference chains. | 5 / 5 |
Total | 17 / 20 Passed |