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.
A well-engineered workflow document: fully sequenced steps with real validation checkpoints and an exemplary progressive-disclosure bundle. Its main cost is token efficiency — key rules (fallbackNodeId matching, tool linkage, when to load gotchas) are repeated across the Overview and Steps 2-3, and a few application steps rely on direction rather than shown code.
Suggestions
Consolidate the fallbackNodeId / exact-id-match guidance into a single Step 3 bullet — it is currently spread across the Overview, a Step 2 field description, and three separate Step 3 bullets, which costs tokens and risks divergence if one copy is edited.
Trim the Overview's tool-linkage paragraph ("The two are linked by node id, and that's the whole workflow…") since Step 3 restates the same merge rules in fuller, actionable form.
For the weakest actionable spots, inline a short concrete pattern for the two directional instructions — mapping a Figma easing to a Motion.dev spring/Bezier within groupDurationMs, and a minimal prefers-reduced-motion snippet — rather than leaving the adaptation fully implicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious Figma-specific signal (no padding with concepts Claude already knows), but carries notable redundancy: fallbackNodeId/exact-id-match rules are explained in the Overview, in Step 2, and again across three separate Step 3 bullets, and the gotchas.md load instruction and Overview tool-linkage paragraph are repeated. This is 'includes some unnecessary explanation or could be tightened' rather than the minor-trim level of anchor 4. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: tool call signatures with parameters, field-by-field response semantics, and specific code patterns (transformTemplate={(_, generated) => "<css> " + generated}, the [45,125,125] → [0,80,80] offset, curl -L asset downloads, the // TODO: <nodeId> format). Minor gaps keep it below anchor 5: worked code examples are delegated to references and a few steps remain directional (e.g., "fit the supplied easing into groupDurationMs, including springs" without showing how). | 4 / 5 |
Workflow Clarity | Five clearly sequenced steps (confirm design context → fetch motion → merge → apply → validate) with explicit validation checkpoints and feedback loops: "reload, observe, iterate" spot-checking before batching (Step 5 and Rule 4), an escalation path for unrepresentable nodes (TODO comment + call out in summary), and an explicit conflict-resolution rule (prefer get_motion_context). | 5 / 5 |
Progressive Disclosure | Clean overview-plus-references structure: six one-level-deep reference files, each verified to exist, with load conditions stated both inline at the point of need ("Load references/gotchas.md before implementing this case") and in an indexed References section; cross-links are sibling-level with back-to-SKILL.md navigation, and deep material (gotchas, worked examples, SVG how-tos, library tables) is appropriately split out of the body. | 5 / 5 |
Total | 17 / 20 Passed |