CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is figma-use-motion in figma/mcp-server-guide

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary skill body: dense with non-obvious operational detail, concrete API names and commands, a well-sequenced verification workflow with feedback loops, and textbook progressive disclosure via a purpose table for two real reference files. The only weakness is the absence of a complete example call payload in the body itself.

Suggestions

Add one compact end-to-end example in the body (e.g., a minimal applyManualKeyframeTrack call with a two-keyframe track object, or a full export_video request) so the most common case is copy-paste ready without opening a reference.

Optionally include one explicit JSON snippet for the export_video polling re-invocation ({ fileKey, jobId }) alongside the ffmpeg frame-extraction command to complete the verification loop.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every line carries non-obvious operational knowledge (the exact gating error string, the export cost model, server clamps, poll mechanics) with zero explanations of concepts Claude already knows. Not 4 because no section can be identified as over-explanation or padding.

5 / 5

Actionability

Highly concrete guidance: exact API signatures (node.applyManualKeyframeTrack(field, track), node.setTimelineDuration(id, seconds)), exact public enum names (EASE_IN_AND_OUT, never EASE_IN_OUT), numeric render params (fps: 5, WIDTH 320), and a copy-paste ffmpeg command. Not 5 because no complete example call payload (e.g., a full manualKeyframeTracks object or export_video invocation) appears in the body — detail is deferred to references — which is a minor gap; not 3 since nothing is vague or pseudocode.

4 / 5

Workflow Clarity

The verification workflow is a clearly numbered plan (pick moments → size → set fps) with an explicit poll loop, an iterate-until-right feedback loop ('fix the keyframes/styles and re-export... batch every fix into one pass before re-rendering'), bail-out-fast error handling for the feature gate, and a pre-flight checklist. Matches the top anchor with feedback loops and checklists.

5 / 5

Progressive Disclosure

Model progressive disclosure: the body is an overview with a 'Doc | When to load | What it covers' table pointing to two real, verified, one-level-deep references (motion-patterns.md, motion-easing.md — the #animatable-fields anchor exists), plus a clear cross-link to the foundational figma-use skill. Nothing that belongs in a reference is inlined.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, and specific, with both a clear capability statement and an explicit 'when to load' trigger clause. Keyword coverage is good with only minor synonym gaps.

DimensionReasoningScore

Specificity

Enumerates several concrete capability areas — 'animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration' — matching the anchor for several specific actions with minor gaps. Not 5 because adjacent operations (removing keyframes/styles, verifying animation output) are not named, leaving slightly incomplete coverage.

4 / 5

Completeness

Explicitly answers both: what ('Motion / animation context for the use_figma MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration') and when ('Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node'). Matches the top anchor with a concrete trigger clause.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'motion', 'animation', 'animating', 'keyframes', 'easing', 'timeline duration', and 'Figma'. Not 5 because common synonyms users might say ('transition', 'fade', 'animate this') are missing; not 3 since coverage clearly exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

A clear niche — motion/animation on Figma nodes via the use_figma tool — explicitly distinguished from the foundational figma-use skill by the 'Load alongside figma-use' scoping. Minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
figma/mcp-server-guide
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.