figma-generate-personal-token

Detect, validate, and persist Figma API tokens to environment files.

4|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ClubMediterranee/ai-core --skill figma-generate-personal-token
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-generate-personal-token
Source: https://github.com/ClubMediterranee/ai-core/tree/main/skills/figma-generate-personal-token
Command: npx skills add https://github.com/ClubMediterranee/ai-core --skill figma-generate-personal-token

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the complete lifecycle of a Figma API token: detection, validation, and persistence to the project .env file, ensuring tokens are available when needed and never manually copied into code.

Core Features & Use Cases

  • Auto-login: uses FIGMA_USERNAME and FIGMA_PASSWORD to generate a token automatically when available.
  • Token validation: checks token validity via Figma API before persisting.
  • Environment management: writes FIGMA_TOKEN to .env (or prioritized .env.local/.env.development files) and warns if .env is not gitignored.
  • Use Case: onboarding a new Figma integration where a valid token must be generated or refreshed before running tasks that call the Figma API.

Quick Start

Run the main script to detect, validate, or generate and persist your Figma token.

Frequently Asked Questions about figma-generate-personal-token

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Figma API token generation and persistence to .env files?

Automating Figma API token generation involves detecting, validating, and persisting the token to environment files. This ensures tokens are available for API access without manual copying, using optional FIGMA_USERNAME and FIGMA_PASSWORD for auto-login.

Can I validate a Figma token against the API before saving it to my environment?

Yes, validating a Figma token against the API before saving it ensures its validity. The process checks the token via the Figma API and then writes the FIGMA_TOKEN to prioritized environment files like .env.local or .env.development.

What is the best way to securely manage Figma tokens in an automation workflow?

Securely managing Figma tokens in an automation workflow requires persisting them to environment files and warning if .env is not gitignored. This prevents manual copying into code and ensures safety during token generation and storage.

Do I need FIGMA_USERNAME and FIGMA_PASSWORD to generate a Figma token?

FIGMA_USERNAME and FIGMA_PASSWORD are optional dependencies required only for auto-login to generate a Figma token automatically. If unavailable, the process can still detect and validate existing tokens for persistence.

Why does my Figma token persistence workflow warn about .env files?

Your Figma token persistence workflow warns about .env files to ensure safety when the .env file is not gitignored. This prevents accidentally committing sensitive FIGMA_TOKEN data to version control during environment management.

Does Figma token validation work with prioritized environment files like .env.local?

Figma token validation works with prioritized environment files by writing the validated FIGMA_TOKEN to .env.local or .env.development. This ensures the token is available for authenticated Figma API access across different environments.