figma

Paste a figma.com link and the Skill routes it by intent: assets render via the REST API as frozen SVG/PNG files, components convert to editable HTML, and motion translates to GSAP timelines. All Figma I/O happens at import time so renders stay deterministic.

Run the tokens command, which degrades to published-style metadata on non-Enterprise plans. With a compatible Figma connector, variable definitions can be retrieved and cached to build the binding index, labeling the import as connector-sourced.

The token needs read-only scopes: File content and File metadata. Add Library content read-only for the published-styles fallback on non-Enterprise plans, and optionally Variables read-only which is Enterprise-only. The integration never writes to Figma.

Motion import has no REST equivalent, so without a compatible connector you must provide a native Figma export such as an MP4, which is frozen and embedded as a video clip. Shader-driven tracks always require a native export since Figma flattens shaders to base colors.

A 403 names the exact missing token scope, such as library content for the styles fallback, or means the file is not visible to the account. A 429 is rate limiting; the client retries automatically with backoff honoring Retry-After, so wait a minute or batch fewer nodes per call.

The verify-motion script compares the render against Figma's own video export using motion-energy PSNR deltas, which cancels out static fidelity differences. It fails below a 15dB minimum motion-PSNR threshold, indicating diverging choreography that needs re-translation.