Figma
SkillFiles & storageLets your agent look up your Figma account, read design file details, and post comments on files.
Then ask your AI: use the Figma skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
About this skill
Look up your Figma user, read file metadata, and post comments on files. Trigger phrases: figma, figma file, design file.
What this skill tells your AI
The instructions your AI receives, as published by anil-matcha/awesome-muse-connectors in connectors/figma/SKILL.md and read by Ahel’s review.
Purpose
Read from the user's Figma: the authenticated user (me) and file metadata (file: name, lastModified, version, thumbnailUrl). The full file document is intentionally not returned: it is too large to be useful in chat, so file surfaces metadata only. The comment command posts a comment to a file (plain text, or anchored to a node with --node-id); positioned canvas pins (x/y without a node) are not supported because the exact client_meta schema is not clearly defined in Figma's public docs.
Tooling
All commands go through bin/figma.py:
bin/figma.py me # authenticated user (handle, email)
bin/figma.py file --key KEY # file metadata: name, lastModified, version, thumbnailUrl
# Comment posts need an exact --confirm string (the CLI prints the required string on refusal)
bin/figma.py comment --key KEY --message "Looks great!" \
--confirm 'post comment on file KEY: "Looks great!"'
bin/figma.py comment --key KEY --node-id 1:42 --message "Spacing looks off here." \
--confirm 'post comment on file KEY: "Spacing looks off here."'
Get the file key from a Figma URL: it is the segment after /file/ or /design/.
Auth
- Provider id:
figma(credential is collected ascustom.figma) - Collection: personal access token via the secure credential flow (
credentials.request_api_access): create one in Figma → Settings → Personal access tokens (needs at least thefile_content:readscope forfile;commentadditionally needsfile_comments:write) - Connect placement:
custom_header:X-Figma-Token(Figma PATs useX-Figma-Token, notAuthorization: Bearer) - Allowed hosts:
api.figma.com - Status check:
bin/figma.py me(a successful response proves the token works)
Operating Rules
commentneeds an exact--confirmstring echoed by the CLI on every post; the CLI prints the required string when it refuses. Reading needs no confirmation.- Only node-anchored (
--node-id) or plain comments ship: raw x/y canvas pins are not supported because Figma'sclient_metaschema is not clearly documented. - Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/figma.py). Do not print, log, or transmit the token value.
Files
- SKILL.md
- bin/figma.py
Maturity
🧪 Draft: written from Figma's public REST API docs (including the post-comment endpoint); not yet live-tested end-to-end.
Signals
- GitHub stars
- 1k
- Forks
- 309
- Last commit
- Oct 2026
- Hacker News mentions
- 20
Ahel review
S4info
community integration, published by anil-matcha, not figma
Automated review, not a security audit. Ruleset v1+k2.
Advanced
- Item type
- skill
- Key
figma-anil-matcha- Source
- github.com/anil-matcha/awesome-muse-connectors
github.com/anil-matcha/awesome-muse-connectors
Related picks
Skill · openai
The pick for Figmaod-figma-migration
Skill · nexu-io
The pick for Figmae2e-testing
Skill · thedaviddias
The pick for End-to-end testinge2e-environment-preflight
Skill · sno-ai
The pick for End-to-end testingdbos-python
Skill · sickn33
The pick for Pythonpython-design-patterns
Skill · wshobson
The pick for Python