SKILLEMALL.ai

BC figma-use-motion

Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node. Also covers working with custom animation styles.

The skillemall take

Promises animation context for Figma nodes via keyframes, styles, and timeline. Five files in the package, but broken_references flag signals missing links inside. Quality score 75 tells the story: instruction is incomplete, animation workflow described but examples or diagrams are broken. No model runs to verify behavior. Works as a reference for those already familiar with Figma API, but newcomers will struggle piecing logic together from fragments. Install if you're already using use_figma and specifically need animation context; for first-time Figma automation, look elsewhere.

figma/mcp-server-guide Claude Code author: figma 5 files body ≈ 2 099 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Motion / animation context for the usefigma MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration.

As a process C 55/100 · Has gaps — References files that are not bundled: ../figma-use/SKILL.md, ../figma-use/SKILL.md

GeneratorFigmaDesignWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
55/100
Has gaps
References files that are not bundled: ../figma-use/SKILL.md, ../figma-use/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../figma-use/SKILL.md
  • warning missing-ref reference to a missing file: ../figma-use/SKILL.md

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: ../figma-use/SKILL.md, ../figma-use/SKILL.md
  • 0Tools and files. 2 referenced file(s) missing: ../figma-use/SKILL.md, ../figma-use/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 7 mutating operations with no state check
  • 85Steps. 28 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2099 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 302: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 28 items
  • +4Reference files are cited in the instructions (4 of 4)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.