# Automate Figma Workflows with Rube MCP

Manual Figma inspection, export, and token extraction consume time and invite inconsistent results. This skill guides Claude, Codex, and Claude Code through structured Rube MCP workflows.

## Install

```bash
npx skillstore add sickn33/figma-automation
```

## Metadata

- Status: approved
- Slug: sickn33-figma-automation
- Skillstore revision: r2
- Version status: missing
- Tree hash: 76d9df4596c33f788eb378f8400b16d97e15ae2c8e32dd3e5ac4d3698e2584aa
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/figma-automation
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-figma-automation
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-figma-automation/manifest

## Capabilities

- Connect to Figma through Rube MCP and verify active authorization.
- Discover resource identifiers from Figma URLs and retrieve file, node, component, and component-set data.
- Render selected nodes as PNG, SVG, JPG, or PDF and download generated images.
- Extract colors, typography, spacing, styles, and variables, with optional Tailwind conversion.
- Read or add file comments, inspect versions, and browse team projects, files, and published styles.

## Use Cases

- Inspect Designs for Implementation: Retrieve pages, nodes, and component metadata before building an interface.
- Extract a Design System: Collect styles and variables, then prepare complete tokens for Tailwind conversion.
- Coordinate Design Reviews: Review comments and versions, then post approved feedback to the Figma file.

## Prompt Templates

### Summarize a Figma File

```
Connect through Rube MCP and summarize the pages and top-level components in [FIGMA_URL]. Use depth 2 and report access errors.
```

### Export Selected Assets

```
Find nodes named [NODE_NAMES] in [FIGMA_URL], render them as [FORMAT] at [SCALE], and provide the available download links.
```

### Prepare Tailwind Tokens

```
Extract local styles and variables from [FIGMA_URL], summarize token groups, then convert the complete token response into a Tailwind configuration.
```

### Audit Components and Feedback

```
Review components, comments, and versions for [FIGMA_URL], identify inconsistencies, and add approved comments only after showing the proposed messages.
```

## Limitations

- Requires configured Rube MCP and active Figma authorization.
- Uses third-party Rube and Composio infrastructure, so users should review permissions and data-handling terms.
- File JSON retrieval supports Figma Design files, not FigJam boards or Figma Slides.
- Large file requests can exceed payload limits, while large renders may be scaled down.

## Best Practices

- Search Rube tools before each workflow because schemas can change.
- Request only required nodes and use a shallow depth before detailed traversal.
- Ask for approval before posting comments or downloading assets to local storage.

## Anti Patterns

- Do not send unreviewed comments or assume write permission.
- Do not request entire deep file trees when specific node identifiers are available.
- Do not reuse expired render URLs or expose them in public channels.

## Security Audit

- Audited at: 2026-07-23T22:06:52.494\+00:00
- Summary: All 49 shell-execution alerts are false positives caused by Markdown backticks around tool names, parameters, URLs, or workflow examples. The six reconnaissance alerts are also false positives. The external Rube MCP connection and authenticated Figma access create a legitimate third-party data and authorization boundary.

## Stats

- Views: 128
- Downloads: 14
- Favorites: 0
- Popularity score: 0