Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/od-figma-migration
Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.
Passed 19 of 23 test cases with the skill, and 7 of 23 without it.
and 17 more in the full report
13 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our Figma migration critique stage JSON object, a developer claims that the repeat property should be omitted or set to false because iteration count is handled inside the atom. What boolean value should repeat be set to?
| Checked | Without skill | With skill |
|---|---|---|
| Sets repeat to true in the critique stage JSON object. | Missed | Passed |
The instructions your model reads when the skill loads.
Spec §1 / §10.1 / §21.3.1 / §23.3.3: the canonical figma-migration
flow. The pipeline is sequenced so each stage's output is the next
stage's input — figma-extract writes figma/tree.json,
token-map writes token-map/colors.json (etc.), and generate
reads both before producing the HTML artifact.
{
"stages": [
{ "id": "extract", "atoms": ["figma-extract"] },
{ "id": "tokens", "atoms": ["token-map"] },
{ "id": "generate", "atoms": ["file-write", "live-artifact"] },
{
"id": "critique", "atoms": ["critique-theater"],
"repeat": true,
"until": "critique.score>=4 || iterations>=3"
}
]
}
The scenario expects two oauth-prompt / form surfaces from the
plugin layer:
figma-oauth — oauth.route='connector', connectorId='figma',
persists at the project tier so multi-conversation work doesn't
re-prompt.file-pick — kind='form', captures the Figma file URL on the
first turn so figma-extract knows where to read.The daemon auto-derives the figma-oauth surface when
od.connectors.required[].id='figma' is declared and the connector
isn't yet authorised (spec §10.3.1 implicit oauth-prompt rule).
test cases passed, vs 7 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.