figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot this file at version X', 'get the file as it was last week', 'diff two Figma versions', 'what changed between these versions', 'compare version A and B', 'did this component change between releases'. Uses the Figma REST API + a personal access token because version history is NOT rea
npx skills add southleft/figma-console-mcp-skills --skill figma-version-history --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# figma-version-history — list, snapshot & diff Figma versions Version history lives only in Figma's **REST API**, so this skill calls REST directly with a personal access token (PAT). It does three things: 1. **List** a file's version history (label, description, author, timestamp, version id). 2. **Snapshot** the file (or just some nodes) as it existed at a given `version_id`. 3. **Diff** two versions — a cheap page-structure diff always, plus optional deep per-component diffs at `depth=2`. > **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 *File versions: read*), 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 b
- Setup & skill boundaries
- Derive the file key
- Workflow
- What the diff DOES and does NOT track
- Notes
echo "$FILE_KEY" # ABC123def456 curl -s -H "X-Figma-Token: $FIGMA_TOKEN" \ node scripts/diff-versions.mjs --file ABC123def456 --from 4096761871 --to current node scripts/diff-versions.mjs --file ABC123def456 --from 4096761871 --to 4096800000 \
What does the figma-version-history skill do?
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot this file at version X', 'get the file as it was last week', 'diff two Figma versions', 'what changed between these versions', 'compare version A and B', 'did this component change between releases'. Uses the Figma REST API + a personal access token because version history is NOT rea
How do I install it?
Run `npx skills add southleft/figma-console-mcp-skills --skill figma-version-history --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.