Agent skill · software engineering · jeremylongshore
figma-upgrade-migration
Handle Figma REST API scope changes, deprecations, and migration tasks.
Why this skill is useful
Adds executable scripts for migrating Figma API scopes and webhooks that are not in public documentation.
What it needs
Requires git installed locally. Requires figma account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Figma Upgrade & Migration Overview Handle Figma REST API deprecations and breaking changes. The most significant recent change is the deprecation of the files:read scope in favor of granular scopes, and the move from Webhooks V1 to V2. Prerequisites Current Figma integration working Git for version control Access to Figma developer settings Instructions Step 1: Scope Migration (files:read Deprecation) The files:read scope is deprecated. Migrate to granular scopes: Deprecated Scope Replacement Scopes Endpoints Covered ----------------- ------------------- ------------------- files:read filecontent:read GET /v1/files/:key, GET /v1/images/:key files:read filecomments:read GET /v1/files/:key/comments files:read filedevresources:read GET /v1/files/:key/devresources files:read fileversions:read GET /v1/files/:key/versions Migration steps: 1. Audit which endpoints your code calls 2. Map each endpoint to its required scope 3. Generate a new PAT with granular scopes 4. Update OAuth apps with new scope list 5. Test all endpoints with the new token 6. Revoke old tokens Step 2: Webhooks V1 to V2 Migration Step 3: OAuth App Publishing Flow All OAuth apps (public and private) must complete the new publishing flow: 1. Go to your app in the Figma developer dashboard 2. Complete the required app information fields 3. Add required redirect URLs 4. Submit for review (public apps) or activate (private apps) 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/figma-upgrade-migration