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.
This skill provides animation context for Figma's use_figma MCP tool, handling keyframe animations, styles, easing, and timeline duration. Three modules included, but code quality sits at 75/100 with only 52% process completion. No critical issues found, though broken references and missing files suggest incomplete implementation. Never tested on actual models.
Install if you're comfortable troubleshooting gaps mid-workflow. For serious Figma animation work, wait for a complete build.
Motion / animation context for the usefigma MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration.
As a process C 52/100 · Has gaps — References files that are not bundled: ../figma-use/SKILL.md, ../figma-use/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../figma-use/SKILL.md - warning
missing-refreference to a missing file: ../figma-use/SKILL.md
Process rating: all ten parameters 52/100
- 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
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 6 mutating operations with no state check
- 85Steps. 24 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 1632 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 252: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 24 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.