How do I install the Figma Library Variables skill?

Run npx skillmds@latest add southleft/figma-library-variables in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Figma Library Variables safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Figma Library Variables?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Figma Library Variables free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Figma Library Variables?

southleft (@southleft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Figma Library Variables by southleft

Name: Figma Library Variables
Author: southleft

Figma Library Variables

Discover and import design tokens from SUBSCRIBED Figma team libraries into the current file. Use when the user wants to reuse tokens that live in a shared library: triggers 'list library variables', 'what tokens are in our shared library', 'import a variable from our design system library', 'pull in the brand color token from the library'. Works on ANY plan via the Plugin API teamLibrary methods. For LOCAL variables use figma-export-tokens / figma-manage-variables.

southleft c7e42cb 3 files · 5.5 KB Updated Sep 17, 2026

File contents

figma-library-variables — discover & import team-library variables

Browse the variables published by libraries the current file subscribes to, then import the ones you need. Imported variables get a local id that behaves like any local variable (bind it, read it, reference it).

Skill boundaries

use_figma rules — load the official figma-use skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level await + return (no IIFE, no figma.closePlugin(); console.log is not returned), inputs inlined as const at the top of each script, colors in 0–1 range, load fonts before any text op, await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).
Local (non-library) variables → figma-export-tokens, figma-manage-variables.

Workflow

Discover. Run scripts/list-library-variables.js via use_figma (skillNames: "figma-library-variables"). Optionally set the LIBRARY_NAME / COLLECTION_NAME / TYPE filters. It returns each subscribed collection and the key of every variable in it.
Import. Put the variable key(s) into scripts/import-library-variable.js and run it. It returns the new localId for each. Re-importing is idempotent (same local id).
Use. Bind the imported variable to node properties or reference it from local semantic tokens (see figma-use / figma-manage-variables for binding).

Notes

Only subscribed libraries appear. If a collection is missing, enable the library in the file's library settings first (a manual Figma step).
getVariablesInLibraryCollectionAsync takes the collection key, not its id.
Library variables are read-only references to the source — edit values in the library file, not here.

---name: figma-library-variablesdescription: Discover and import design tokens from SUBSCRIBED Figma team libraries into the current file. Use when the user wants to reuse tokens that live in a shared library: triggers 'list library variables', 'what tokens are in our shared library', 'import a variable from our design system library', 'pull in the brand color token from the library'. Works on ANY plan via the Plugin API teamLibrary methods. For LOCAL variables use figma-export-tokens / figma-manage-variables.---# figma-library-variables — discover & import team-library variablesBrowse the variables published by libraries the current file subscribes to, then import the ones youneed. Imported variables get a local id that behaves like any local variable (bind it, read it,reference it).## Skill boundaries- **`use_figma` rules** — load the official **`figma-use`** skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level `await` + `return` (no IIFE, no `figma.closePlugin()`; `console.log` is not returned), inputs inlined as `const` at the top of each script, colors in 0–1 range, load fonts before any text op, `await figma.getNodeByIdAsync(...)`, and **atomic errors** (a failed script applies nothing — read the error, fix, retry).- Local (non-library) variables → `figma-export-tokens`, `figma-manage-variables`.## Workflow1. **Discover.** Run [`scripts/list-library-variables.js`](scripts/list-library-variables.js) via `use_figma` (`skillNames: "figma-library-variables"`). Optionally set the `LIBRARY_NAME` / `COLLECTION_NAME` / `TYPE` filters. It returns each subscribed collection and the `key` of every variable in it.2. **Import.** Put the variable `key`(s) into [`scripts/import-library-variable.js`](scripts/import-library-variable.js) and run it. It returns the new `localId` for each. Re-importing is idempotent (same local id).3. **Use.** Bind the imported variable to node properties or reference it from local semantic tokens (see `figma-use` / `figma-manage-variables` for binding).## Notes- Only **subscribed** libraries appear. If a collection is missing, enable the library in the file's library settings first (a manual Figma step).- `getVariablesInLibraryCollectionAsync` takes the **collection key**, not its id.- Library variables are read-only references to the source — edit values in the library file, not here.

Frequently asked questions