CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

91%

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

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 excellent content body: every section carries Figma-specific knowledge Claude could not infer (gating errors, public vs. internal names, render cost mechanics), the verification workflow has explicit validation and feedback loops, and detail is properly deferred to five well-signaled, verified reference files. Only minor tightening opportunities remain, chiefly the repeated "make each render count" phrasing.

DimensionReasoningScore

Conciseness

Dense, high-signal guidance that assumes competence — public vs. internal API names, gating behavior, render cost model — with no teaching of known concepts. Anchor 4 rather than 5 because "make each render count" is repeated nearly verbatim and a few rationale sentences ("Otherwise you'll burn calls and confuse the user with repeated identical failures") could be trimmed.

4 / 5

Actionability

Fully executable throughout: exact enums ("never emit the invalid alias EASE_IN_OUT"), concrete parameters ("constraint: { type: 'WIDTH', value: 320 }", "quality: \"low\"", "fps: 5"), a copy-paste frame-extraction command ("ffmpeg -ss <t> -i anim.mp4 -frames:v 1 frame_<t>.png"), and polling mechanics ("re-invoke with { fileKey, jobId }"). Matches anchor 5 — copy-paste ready and covers the common cases.

5 / 5

Workflow Clarity

The verification workflow is clearly sequenced (pick moments → size → fps → export → poll → extract → iterate) with an explicit feedback loop ("fix the keyframes/styles and re-export... batch every fix into one pass"), a defined failure path ("Bail out fast on that error. Do not retry"), and a 9-item pre-flight checklist. Matches anchor 5: explicit validation steps, error-recovery loops, and a checklist.

5 / 5

Progressive Disclosure

The body is a genuine overview (~90 lines): API surface, gating, verification workflow, and a reference table giving "When to load" and "What it covers" for each of five docs. All five referenced files exist, are one level deep, and the deep link anchor (#animatable-fields) matches a real heading in motion-patterns.md. Matches anchor 5 — clear overview with well-signaled one-level-deep references.

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 with an explicit what-and-when structure, concrete capability enumeration, and natural trigger phrasing, all in third person. The only weakness is a coverage gap: text animation (typewriter reveals, staggering) is a first-class capability of the skill but never surfaced in the description, costing it both specificity and trigger-term breadth.

Suggestions

Add text animation to the capability list, e.g. "animating characters/words/lines within editable text (typewriter reveals, staggered text)" — this closes the specificity gap and adds the natural trigger terms "typewriter" and "stagger".

Include one or two user-facing synonyms such as "transition" or "text reveal" in the trigger phrasing so the description fires on how users naturally ask for these effects.

DimensionReasoningScore

Specificity

Names five concrete capability areas — "manual keyframes, animation styles, easing, and timeline duration" plus "custom animation styles" — but omits text animation/typewriter/stagger, a major capability the skill itself covers with a dedicated reference file. Closest to anchor 4 (several specific actions, minor gaps), not 5 (comprehensive) because of that omission and not 3 (only 1-2 actions) because coverage well exceeds two actions.

4 / 5

Completeness

Explicitly answers both: what ("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") with concrete trigger phrasing. Matches anchor 5; not 4 because the when-clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "motion / animation", "animating", "keyframes", "easing", and the trigger phrase "whenever a task involves adding, editing, or inspecting animation on a node". Good coverage but missing natural variations like "typewriter", "text reveal", "stagger", or "transition", which keeps it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to the `use_figma` MCP tool's motion domain and explicitly positioned as a companion to figma-use ("Load alongside figma-use"), with the body further excluding static design work. Clear niche with distinct triggers and minimal conflict risk — anchor 5.

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

Path

skills-figquery/figma-use-motion/SKILL.md

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.