Agent skill · design visual · aiskillstore
figma-automation
Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
Why this skill is useful
Adds specific commands and workflows for automating Figma tasks that the AI wouldn't reliably generate on its own.
What it needs
Requires rube installed locally. Requires figma account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Figma Automation via Rube MCP Automate Figma operations through Composio's Figma toolkit via Rube MCP. Prerequisites Rube MCP must be connected (RUBESEARCHTOOLS available) Active Figma connection via RUBEMANAGECONNECTIONS with toolkit figma Always call RUBESEARCHTOOLS first 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. 1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds 2. Call RUBEMANAGECONNECTIONS with toolkit figma 3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth 4. 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: 1. FIGMADISCOVERFIGMARESOURCES - Extract IDs from Figma URLs [Prerequisite] 2. FIGMAGETFILEJSON - Get file data (simplified by default) [Required] 3. FIGMAGETFILENODES - Get specific node data [Optional] 4. FIGMAGETFILECOMPONENTS - List published components [Optional] 5. FIGMAGETFILECOMPONENTSETS - List component sets [Optional] Key parameters: filekey: 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 ids must 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 datapreview instead of data 2. Export and Render Images When to use: User wants to export design assets as images Tool sequence: 1. FIGMAGETFILEJSON - Find node IDs to export [Prerequisite] 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/figma-automation