Agent skill · Backend & API

figma-comments

Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a comment on this node', 'reply to a Figma comment', 'pin a comment to this element', 'delete a Figma comment', 'notify designers of drift', 'add a review note in Figma'. Uses the Figma REST API + a personal access token because comments are NOT reachable via the Plugin API / use_figma

southleftgithub.com/southleftGitHub ↗
claude-codeships scriptsMIT
Install
npx skills add southleft/figma-console-mcp-skills --skill figma-comments --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 5 KB
Bundled scripts: yes
Path: skills/figma-comments/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 67
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# figma-comments — read, post, reply & delete Figma comments Comments live only in Figma's **REST API** — the Plugin API (`use_figma`) and the native Figma MCP can't touch them. This skill reads comment threads, posts new comments (optionally pinned to a node), replies to existing threads, and deletes comments. > **Setup — terminal + token required.** This skill runs shell commands, so it works in **Claude Code** (including the "Code" tab inside Claude Desktop), Cursor, Codex, or Gemini CLI — it does **not** run in plain Claude Desktop or claude.ai chat (no shell). The Figma connector's OAuth login does **not** authorize these REST calls, so you must supply your own **Figma personal access token**: in Figma go to **Settings → Security → Personal access tokens**, generate one with scope *File content: read* (plus *Comments: read/write*), then set it in your shell: `export FIGMA_TOKEN="figd_…"`. The script reads it from the environment at runtime — never put the token in a skill file. ## Setup & skill boundaries - All requests use `X-Figma-Token: $FIGMA_TOKEN` against `https://api.figma.com`. - **`@mentions` are a Figma UI-only feature.** Putting `@name` in a message renders as plain

What's inside
Steps it walks through
  1. Setup & skill boundaries
  2. Derive the file key
  3. Read comments
  4. Post a comment
  5. Delete a comment
  6. Notes
Ships with 3 files
  • scripts/delete-comment.sh
  • scripts/get-comments.sh
  • scripts/post-comment.sh
Commands it runs
curl -s -H "X-Figma-Token: $FIGMA_TOKEN" \
Plain file-level comment
Pinned to a node (appears on that element). x/y default to 0,0 if omitted.
Reply to an existing thread (get IDs from get-comments.sh)
curl -s -X POST -H "X-Figma-Token: $FIGMA_TOKEN" -H "Content-Type: application/json" \
curl -s -X DELETE -H "X-Figma-Token: $FIGMA_TOKEN" \
More from figma-console-mcp-skills
All skills →
figma-analyze-component-setAnalyze a Figma COMPONENT_SET as a state machine for code generation — extract variant axes…Frontendfigma-annotationsRead and write designer annotations on Figma nodes — node-level design specs that pin properties…Frontendfigma-arrange-component-setOrganize a Figma COMPONENT_SET's variants into a clean, labeled grid — rows and columns derived…Frontendfigma-audit-accessibilityDeep accessibility scorecard for a single Figma component or component set — state coverage…Securityfigma-blame-nodeFind which Figma version introduced a specific change — a component property or a child node — via…Frontendfigma-check-design-parityCompare a Figma node's actual specs against a code spec (the values your component renders) and get…Testing & QA
About this skill
What does the figma-comments skill do?

Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a comment on this node', 'reply to a Figma comment', 'pin a comment to this element', 'delete a Figma comment', 'notify designers of drift', 'add a review note in Figma'. Uses the Figma REST API + a personal access token because comments are NOT reachable via the Plugin API / use_figma

How do I install it?

Run `npx skills add southleft/figma-console-mcp-skills --skill figma-comments --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From southleft/figma-console-mcp-skills, a repository with 67 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.