Figma Plugin API Operator
Helps agents safely read and write Figma files by rule.
The skill explicitly routes JavaScript execution through the Figma MCP, and documents output handling, incremental changes, node-ID tracking, stop-on-error behavior, and variable scoping. It does not document user confirmation, sensitive-data handling, permission isolation, rollback, or data-flow boundaries, and it depends on an external Figma service, so points were deducted.
SKILL.md gives substantial guidance on API limitations, page context, error recovery, and validation. However, common-patterns.md and several reference examples still use async IIFEs and closePlugin, contradicting the main rules; there are also no committed tests or reproducible execution records. Static calibration therefore limits the score.
Invocation triggers, intended audience, and major use cases are relatively clear for Figma reads, writes, variables, components, and layouts. Chinese-language support is not documented, the core dependency is an overseas Figma MCP service, and fallback behavior for unreachable networks or unavailable Figma environments is unclear.
The documentation is layered across rules, page behavior, workflows, recovery, and reference material; maintainers.yml identifies mcp_server and many examples are provided. License, version, changelog, maintenance responsibility, update path, installation guidance, and troubleshooting coverage remain incomplete, so points were deducted.
The skill provides concrete API constraints, incremental workflows, validation guidance, and common-error handling that could directly support Figma operations. Static files do not demonstrate successful completion of key paths, and contradictory examples may create rework, so the score remains below the upper static limit.
The evidence consists mainly of auditable repository documentation, reference material, and configuration. There is no committed test suite covering key paths, CI execution evidence, or independent corroboration; contradictory examples further reduce confidence, so only limited points were awarded.
- SKILL.md requires top-level await and return, but multiple reference examples use async IIFEs and closePlugin; the runtime convention should be reconciled before use.
- Core functionality depends on https://mcp.figma.com/mcp, with no documented fallback or offline path for mainland-China network inaccessibility.
- User confirmation, data flow, permission scope, and rollback are not clearly specified; the caller should establish these controls before write operations.
- License, version, and changelog information are not evident, so maintenance and compatibility status require separate verification.
What it does & when to use it
figma-use is an Agent Skill for working with the Figma Plugin API. It requires the skill to be loaded before every use_figma call and uses use_figma to execute JavaScript in a Figma file context. Its guidance covers nodes, variables, components, auto layout, styles, and page switching. It fits programmatic Figma creation, editing, deletion, and inspection workflows, provided the use_figma MCP is available.
It defines how an agent must call use_figma and requires skillNames: "figma-use" on every call. The agent can then execute JavaScript in Figma's file context to inspect pages, nodes, components, and variables; create or modify nodes, variables, and components; and return JSON-serializable data. Every canvas mutation must return affected node IDs. Complex work is split across calls and validated with metadata or screenshots.
- A designer needs to create or edit layers, components, or variants in Figma programmatically.
- A design-system maintainer needs to create variables, define variable scopes, or bind variables to properties.
- A product or frontend team needs to automate auto layout, fills, text, or effect-style changes.
- An automation agent needs to inspect Figma page structure and continue work on identified nodes across calls.
Pros & cons
- Provides extensive operational rules and error-handling guidance for the Figma Plugin API.
- Promotes inspection, incremental execution, and validation for complex workflows.
- Requires node IDs to be returned, supporting follow-up calls, validation, and cleanup.
- Requires the use_figma MCP; the skill text alone cannot operate on a Figma file.
- The supplied material provides no test results, platform support matrix, or standalone license information.
- Full-page layout work also requires the separate figma-generate-design skill.
How to install
The README says curated skills can be installed in Codex with $skill-installer figma-use; restart Codex afterward. The supplied material does not document installation for other clients.
How to use
Load figma-use first, then request a Figma operation such as “Create an auto-layout component in the current Figma file and return every new node ID.” For a full page or multi-section layout, also load figma-generate-design. Every use_figma call must include skillNames: "figma-use".