Agent skill

Figma CI Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Automate Figma design token sync and asset export in CI/CD pipelines.

MITAuto-check passedDevOps & Cloud

Install Figma CI Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill figma-ci-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace figma-ci-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/figma-ci-integration .claude/skills/figma-ci-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
figma-ci-integration
GitHub stars
2.8k
Token cost
~1.5k tokens
SKILL.md length
199 words
Files
6 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Automate Figma design token sync and asset export in CI/CD pipelines.

  • Works in 4 steps: Scheduled Token Sync Workflow → Asset Export on PR → Design System Validation → …
  • Setting up GitHub Actions for Figma
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Calls gh; needs FIGMA_FILE_KEY and FIGMA_ICON_FILE_KEY

What it does

Figma CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Automate Figma design token sync and asset export in CI/CD pipelines. Use when setting up GitHub Actions for Figma, automating icon exports, or validating design token changes in pull requests. Trigger with phrases like "figma CI", "figma GitHub Actions", "automate figma export", "figma CI pipeline".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/asset-export-on-pr.md`, `references/design-system-validation.md` and `references/errors.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering CI/CD, Design tokens and Pull requests. It works with Figma, GitHub Actions and GitHub. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Setting up GitHub Actions for Figma
  • Automating icon exports
  • Validating design token changes in pull requests
  • With phrases like figma CI

Example prompts

  • “figma CI”
  • “figma GitHub Actions”
  • “automate figma export”
  • “/figma-ci-integration”

Requirements

  • A credential in FIGMA_FILE_KEY
  • A credential in GITHUB_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(gh:*)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Scheduled Token Sync Workflow
  2. Asset Export on PR
  3. Design System Validation
  4. Store Figma Secrets

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(gh:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.github.com
    • developers.figma.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • FIGMA_FILE_KEY
    • FIGMA_ICON_FILE_KEY
    • GH_TOKEN
    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Figma CI Integration loads about 1.5k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 199 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 199 words, ~1,538 tokens.

Download SKILL.mdSave it as .claude/skills/figma-ci-integration/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
figma-ci-integration
description
Automate Figma design token sync and asset export in CI/CD pipelines. Use when setting up GitHub Actions for Figma, automating icon exports, or validating design token changes in pull requests. Trigger with phrases like "figma CI", "figma GitHub Actions", "automate figma export", "figma CI pipeline".
allowed-tools
Read, Write, Edit, Bash(gh:*)
compatibility
Designed for Claude Code
version
1.6.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, figma

Figma CI Integration

Overview

Automate Figma API workflows in CI/CD: sync design tokens on schedule, export assets on PR, and validate design system consistency.

Prerequisites

  • GitHub repository with Actions enabled
  • FIGMA_PAT stored as GitHub secret
  • Design token extraction script (from figma-core-workflow-a)

Instructions

Step 1: Scheduled Token Sync Workflow
yaml
# .github/workflows/figma-token-sync.yml
name: Sync Figma Design Tokens

on:
  schedule:
    - cron: '0 9 * * 1-5'  # Weekdays at 9am UTC
  workflow_dispatch:          # Manual trigger

jobs:
  sync-tokens:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'

      - run: npm ci

      - name: Extract tokens from Figma
        env:
          FIGMA_PAT: ${{ secrets.FIGMA_PAT }}
          FIGMA_FILE_KEY: ${{ vars.FIGMA_FILE_KEY }}
        run: node scripts/extract-figma-tokens.mjs

      - name: Check for changes
        id: diff
        run: |
          git diff --quiet src/styles/tokens.css || echo "changed=true" >> $GITHUB_OUTPUT

      - name: Create PR with token updates
        if: steps.diff.outputs.changed == 'true'
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          BRANCH="figma/token-sync-$(date +%Y%m%d)"
          git checkout -b "$BRANCH"
          git add src/styles/tokens.css
          git commit -m "chore: sync design tokens from Figma"
          git push origin "$BRANCH"
          gh pr create \
            --title "Sync design tokens from Figma" \
            --body "Automated token sync from Figma file. Review the CSS changes." \
            --label "design-tokens,automated"
Step 2: Asset Export on PR
yaml
# .github/workflows/figma-asset-export.yml
name: Export Figma Assets

on:
  pull_request:
    paths:
      - 'figma-config.json'  # Trigger when asset config changes

jobs:
  export-assets:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20' }
      - run: npm ci

      - name: Export icons from Figma
        env:
          FIGMA_PAT: ${{ secrets.FIGMA_PAT }}
          FIGMA_FILE_KEY: ${{ vars.FIGMA_ICON_FILE_KEY }}
          FIGMA_ICON_FRAME: ${{ vars.FIGMA_ICON_FRAME_ID }}
        run: node scripts/export-figma-icons.mjs

      - name: Commit exported assets
        run: |
          git add assets/icons/
          if ! git diff --cached --quiet; then
            git config user.name "github-actions[bot]"
            git config user.email "github-actions[bot]@users.noreply.github.com"
            git commit -m "chore: export icons from Figma"
            git push
          fi
Step 3: Design System Validation
yaml
      - name: Validate design tokens
        run: |
          # Check that all CSS custom properties are valid
          node -e "
            const fs = require('fs');
            const css = fs.readFileSync('src/styles/tokens.css', 'utf-8');
            const vars = css.match(/--[\w-]+:/g) || [];
            console.log('Token count:', vars.length);
            if (vars.length < 10) {
              console.error('Too few tokens extracted -- possible Figma API error');
              process.exit(1);
            }
            // Check for duplicate variable names
            const dupes = vars.filter((v, i) => vars.indexOf(v) !== i);
            if (dupes.length > 0) {
              console.error('Duplicate tokens:', dupes);
              process.exit(1);
            }
          "
Step 4: Store Figma Secrets
bash
# Add PAT as repository secret
gh secret set FIGMA_PAT --body "figd_your-token-here"

# Add file key as repository variable (not secret -- it's not sensitive)
gh variable set FIGMA_FILE_KEY --body "abc123XYZdefaultFileKey"
gh variable set FIGMA_ICON_FILE_KEY --body "def456IconFileKey"
gh variable set FIGMA_ICON_FRAME_ID --body "123:456"

Output

  • Scheduled CI job syncing design tokens from Figma
  • Asset export triggered by config changes
  • Token validation preventing broken deployments
  • PR-based workflow for reviewing design changes

Error Handling

IssueCauseSolution
403 in CIPAT expiredRotate secret: gh secret set FIGMA_PAT
Empty token outputFile key wrongVerify FIGMA_FILE_KEY variable
Rate limited in CIConcurrent workflowsAdd concurrency group to workflow
Stale cacheNode modules cachedClear with actions/cache invalidation

Examples

Trigger the Step 1 token-sync workflow manually and verify it opens a PR only when tokens changed:

bash
gh workflow run figma-token-sync.yml
gh run watch && gh pr list --label design-tokens
text
#142  chore(tokens): sync design tokens from Figma  design-tokens  open

The diff shows exactly what changed in the design file:

diff
- "color-brand-primary": "#4338ca",
+ "color-brand-primary": "#4f46e5",

No-change runs exit green without a PR (idempotent by design). Asset export on PR and the validation gate: references/asset-export-on-pr.md, references/design-system-validation.md.

Resources

Next Steps

For deployment patterns, see figma-deploy-integration.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/.curated/figma-ci-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/asset-export-on-pr.md
  • references/design-system-validation.md
  • references/errors.md
  • references/scheduled-token-sync-workflow.md
  • references/store-figma-secrets.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Figma CI Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Figma CI Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Figma CI Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated safety check: PassMIT
ONNX Runtime CI Managementmicrosoft/onnxruntime22k—~4.1kAutomated safety check: PassMIT
CIaiblueprinthq/ai-blueprint463—~2.2kAutomated safety check: PassMIT
CI CDbabarot/gh-infra136—~1.2kAutomated safety check: PassMIT
Michel Monitor Pull Request GitHub ActionsPackmindHub/packmind318—~2.6kAutomated safety check: PassApache-2.0
CIopenJiuwen-ai/sciencediscovery159—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • ONNX Runtime CI Management

    microsoft/onnxruntime

    Official

    Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.

    22k GitHub stars~4.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • CI

    aiblueprinthq/ai-blueprint

    Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook.

    463 GitHub stars~2.2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • CI CD

    babarot/gh-infra

    CI/CD integration for gh-infra in GitHub Actions: plan each pull request and post the plan as a comment, apply on merge, scheduled drift detection with notification, --changed-since and…

    136 GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Diagnose a failed, stuck, or never-triggered CI run on a GitHub PR, apply a local fix if possible, push it, and document the result in a single running PR comment.

    318 GitHub stars~2.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • CI

    openJiuwen-ai/sciencediscovery

    Read, diagnose, and change the CI pipeline: GitHub Actions on pull requests, the nightly schedule and the release tag.

    159 GitHub stars~2.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Diy Netlify

    swyxio/skills

    Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider.

    176 GitHub stars~1.1k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Figma CI Integration

What does Figma CI Integration do?

Automate Figma design token sync and asset export in CI/CD pipelines. Figma CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Automate Figma design token sync and asset export in CI/CD pipelines.

When should I use Figma CI Integration?

Figma CI Integration fits situations like: setting up GitHub Actions for Figma; automating icon exports; validating design token changes in pull requests; with phrases like figma CI.

How do I install Figma CI Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill figma-ci-integration -a claude-code`. Or copy the skill folder (skills/.curated/figma-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/figma-ci-integration in your project. Claude Code loads it when a task matches its description.

How do I install Figma CI Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill figma-ci-integration -a codex`. Or copy the skill folder (skills/.curated/figma-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/figma-ci-integration in your project. Codex loads it when a task matches its description.

Can I use Figma CI Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill figma-ci-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/figma-ci-integration, .gemini/skills/figma-ci-integration, .github/skills/figma-ci-integration and .opencode/skills/figma-ci-integration in your project.

What does Figma CI Integration need to run?

Going by SKILL.md and its folder, Figma CI Integration needs the command-line tools its instructions call (gh) and credentials named FIGMA_FILE_KEY, FIGMA_ICON_FILE_KEY, GH_TOKEN and GITHUB_TOKEN. Our summary lists: A credential in FIGMA_FILE_KEY; A credential in GITHUB_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(gh:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Figma CI Integration access the network?

SKILL.md names 2 domains. As links in the text: docs.github.com and developers.figma.com. This is read from the text; nothing was executed.

Is Figma CI Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Figma CI Integration use?

Figma CI Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Figma CI Integration use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Figma CI Integration?

Skills that share tags, products or a category with Figma CI Integration: ONNX Runtime CI Management (microsoft/onnxruntime, 22k stars), CI (aiblueprinthq/ai-blueprint, 463 stars), CI CD (babarot/gh-infra, 136 stars) and Michel Monitor Pull Request GitHub Actions (PackmindHub/packmind, 318 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Figma CI Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.