Install the catalogue and invoke a skill in a few minutes.
Prerequisites
- Node.js with
npx available (for skills.sh).
- An agent that supports skill invocation.
- A Figma file you can select frames or components in — skills are selection-first.
Install the catalogue
From your project directory:
- Choose skills from the Figma catalogue.
- Choose the agents where you want them installed.
- Invoke a skill by name or by describing the task it covers.
List discoverable skills
From a clean directory, dry-run the catalogue to see what would install:
Only packages under skills/figma-agent/ are discoverable. Everything under archive/ is documentation-only and never appears.
Invoke a skill
Two invocation styles work with any compatible agent:
- By name. “Run
accessibility-audit on the selected frame.”
- By task description. “Audit the current selection for WCAG 2.2 AA basics that are checkable in Figma.” The agent matches the description to
SKILL.md frontmatter and picks the right skill.
Every skill assumes the current Figma selection as its default scope. If nothing is selected, the skill uses the current page and asks before file-wide edits.
Suggested starting set
If you are installing for the first time, these six skills cover the most common loops:
Fast defaults every skill follows
- Start from the selected frame, component, section, or comment thread. If the user named a scope, use that instead of scanning the whole file.
- Do a useful first pass without waiting for perfect context; state assumptions briefly.
- Prefer in-file evidence (exact layers, frames, variables, styles) over generic best practices.
- For report-only prompts, don’t alter the file. For fix or apply prompts, make only scoped, reversible edits unless the user approves broader changes.
- Ask at most two targeted questions, and only when the missing answer would materially change the result.
Next steps
Last modified on August 9, 2026
