SKILLEMALL.ai

BC figma-implement-motion

Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.

The skillemall take

Converts Figma animations into production code. Promises to extract motion data and generate ready-to-use implementation. Grade B: quality 75, process 54. No critical errors, but broken file references suggest some instructions point to missing assets. Seven files, nearly 6K tokens.

Triggers on Figma URLs with animated nodes or explicit commands like "animate this component". Works across Claude, Cursor, DeepSeek, and others. The low process score hints at issues in function call logic. Install it, but prepare to manually fix generated output occasionally.

anomalyco/opencode Claude Code author: anomalyco MIT 7 files body ≈ 5 679 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Translates Figma motion and animations into production-ready application code.

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

ProcedureFigmaDesigntype 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
54/100
Has gaps
References files that are not bundled: ../figma-use/SKILL.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: opencode

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. 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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5679 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../figma-use/SKILL.md

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: ../figma-use/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../figma-use/SKILL.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Steps. 51 steps, 4 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5679 tokens
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (4 tags): a typed call is more reliable

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

  • +4Description does not say when NOT to use the skill (false activations)
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 373: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 51 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)

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