figma-version-historylisted

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 reachable via the Plugin API / use_figma / the native Figma MCP. For a prose release-notes writeup use figma-generate-changelog; to find which version introduced a change use figma-blame-node.
whiskfernlowdensitylipoprotein154/figma-console-mcp-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill whiskfernlowdensitylipoprotein154/figma-console-mcp-skills

# 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 boundaries - All requests go to `https://api.figma.com` with the header `X-Figma-Token: $FIGMA_TOKEN`. - Endpoint reference: [references/endpoints.md](references/endpoints.md). ## Derive the file key The file key is the path segment after `/design/` or `/file/` in a Figma URL: ```bash FILE