figma-automation
Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
Install / Use
npx skills add davepoon/buildwithclaude --skill figma-automationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of figma-automation
figma-automation scores 92/100 on our quality scale, 799th of 2,790 Automation skills we index (top 29%).
Its SKILL.md is 6.9 KB long, well organised into 14 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 3,752 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated today, so figma-automation is actively maintained.
- Our last check on 2026-10-27 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
figma-automation compared with similar skills
All 4 of these similar skills score higher than figma-automation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| figma-automation (this skill)by davepoon | 92 | 3.8k | today | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install figma-automation?
- Run
npx skills add davepoon/buildwithclaude --skill figma-automation. The install tabs above show the steps for each supported agent. - Which AI agents does figma-automation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is figma-automation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is figma-automation still maintained?
- The repository was last updated today, so figma-automation is actively maintained.
Skill content
View source on GitHubname: figma-automation description: "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas." requires: mcp: [rube] category: design
Figma Automation via Rube MCP
Automate Figma operations through Composio's Figma toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/figma
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Figma connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfigma - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitfigma - If connection is not ACTIVE, follow the returned auth link to complete Figma auth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Get File Data and Components
When to use: User wants to inspect Figma design files or extract component information
Tool sequence:
FIGMA_DISCOVER_FIGMA_RESOURCES- Extract IDs from Figma URLs [Prerequisite]FIGMA_GET_FILE_JSON- Get file data (simplified by default) [Required]FIGMA_GET_FILE_NODES- Get specific node data [Optional]FIGMA_GET_FILE_COMPONENTS- List published components [Optional]FIGMA_GET_FILE_COMPONENT_SETS- List component sets [Optional]
Key parameters:
file_key: File key from URL (e.g., 'abc123XYZ' from figma.com/design/abc123XYZ/...)ids: Comma-separated node IDs (NOT an array)depth: Tree traversal depth (2 for pages and top-level children)simplify: True for AI-friendly format (70%+ size reduction)
Pitfalls:
- Only supports Design files; FigJam boards and Slides return 400 errors
idsmust be a comma-separated string, not an array- Node IDs may be dash-formatted (1-541) in URLs but need colon format (1:541) for API
- Broad ids/depth can trigger oversized payloads (413); narrow scope or reduce depth
- Response data may be in
data_previewinstead ofdata
2. Export and Render Images
When to use: User wants to export design assets as images
Tool sequence:
FIGMA_GET_FILE_JSON- Find node IDs to export [Prerequisite]FIGMA_RENDER_IMAGES_OF_FILE_NODES- Render nodes as images [Required]FIGMA_DOWNLOAD_FIGMA_IMAGES- Download rendered images [Optional]FIGMA_GET_IMAGE_FILLS- Get image fill URLs [Optional]
Key parameters:
file_key: File keyids: Comma-separated node IDs to renderformat: 'png', 'svg', 'jpg', or 'pdf'scale: Scale factor (0.01-4.0) for PNG/JPGimages: Array of {node_id, file_name, format} for downloads
Pitfalls:
- Images return as node_id-to-URL map; some IDs may be null (failed renders)
- URLs are temporary (valid ~30 days)
- Images capped at 32 megapixels; larger requests auto-scaled down
3. Extract Design Tokens
When to use: User wants to extract design tokens for development
Tool sequence:
FIGMA_EXTRACT_DESIGN_TOKENS- Extract colors, typography, spacing [Required]FIGMA_DESIGN_TOKENS_TO_TAILWIND- Convert to Tailwind config [Optional]
Key parameters:
file_key: File keyinclude_local_styles: Include local styles (default true)include_variables: Include Figma variablestokens: Full tokens object from extraction (for Tailwind conversion)
Pitfalls:
- Tailwind conversion requires the full tokens object including total_tokens and sources
- Do not strip fields from the extraction response before passing to conversion
4. Manage Comments and Versions
When to use: User wants to view or add comments, or inspect version history
Tool sequence:
FIGMA_GET_COMMENTS_IN_A_FILE- List all file comments [Optional]FIGMA_ADD_A_COMMENT_TO_A_FILE- Add a comment [Optional]FIGMA_GET_REACTIONS_FOR_A_COMMENT- Get comment reactions [Optional]FIGMA_GET_VERSIONS_OF_A_FILE- Get version history [Optional]
Key parameters:
file_key: File keyas_md: Return comments in Markdown formatmessage: Comment textcomment_id: Comment ID for reactions
Pitfalls:
- Comments can be positioned on specific nodes using client_meta
- Reply comments cannot be nested (only one level of replies)
5. Browse Projects and Teams
When to use: User wants to list team projects or files
Tool sequence:
FIGMA_GET_PROJECTS_IN_A_TEAM- List team projects [Optional]FIGMA_GET_FILES_IN_A_PROJECT- List project files [Optional]FIGMA_GET_TEAM_STYLES- List team published styles [Optional]
Key parameters:
team_id: Team ID from URL (figma.com/files/team/TEAM_ID/...)project_id: Project ID
Pitfalls:
- Team ID cannot be obtained programmatically; extract from Figma URL
- Only published styles/components are returned by team endpoints
Common Patterns
URL Parsing
Extract IDs from Figma URLs:
1. Call FIGMA_DISCOVER_FIGMA_RESOURCES with figma_url
2. Extract file_key, node_id, team_id from response
3. Convert dash-format node IDs (1-541) to colon format (1:541)
Node Traversal
1. Call FIGMA_GET_FILE_JSON with depth=2 for overview
2. Identify target nodes from the response
3. Call again with specific ids and higher depth for details
Known Pitfalls
File Type Support:
- GET_FILE_JSON only supports Design files (figma.com/design/ or figma.com/file/)
- FigJam boards (figma.com/board/) and Slides (figma.com/slides/) are NOT supported
Node ID Formats:
- URLs use dash format:
node-id=1-541 - API uses colon format:
1:541
Quick Reference
| Task | Tool Slug | Key Params | |------|-----------|------------| | Parse URL | FIGMA_DISCOVER_FIGMA_RESOURCES | figma_url | | Get file JSON | FIGMA_GET_FILE_JSON | file_key, ids, depth | | Get nodes | FIGMA_GET_FILE_NODES | file_key, ids | | Render images | FIGMA_RENDER_IMAGES_OF_FILE_NODES | file_key, ids, format | | Download images | FIGMA_DOWNLOAD_FIGMA_IMAGES | file_key, images | | Get component | FIGMA_GET_COMPONENT | file_key, node_id | | File components | FIGMA_GET_FILE_COMPONENTS | file_key | | Component sets | FIGMA_GET_FILE_COMPONENT_SETS | file_key | | Design tokens | FIGMA_EXTRACT_DESIGN_TOKENS | file_key | | Tokens to Tailwind | FIGMA_DESIGN_TOKENS_TO_TAILWIND | tokens | | File comments | FIGMA_GET_COMMENTS_IN_A_FILE | file_key | | Add comment | FIGMA_ADD_A_COMMENT_TO_A_FILE | file_key, message | | File versions | FIGMA_GET_VERSIONS_OF_A_FILE | file_key | | Team projects | FIGMA_GET_PROJECTS_IN_A_TEAM | team_id | | Project files | FIGMA_GET_FILES_IN_A_PROJECT | project_id | | Team styles | FIGMA_GET_TEAM_STYLES | team_id | | File styles | FIGMA_GET_FILE_STYLES | file_key | | Image fills | FIGMA_GET_IMAGE_FILLS | file_key |
Powered by Composio
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
