figma-automation
Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
75
Quality
63%
Does it follow best practices?
Impact
96%
2.34xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/figma-automation/SKILL.mdDiscovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear niche (Figma automation via specific tooling) and lists capability categories, but lacks explicit trigger guidance for when Claude should select this skill. The capabilities are listed at a category level rather than as specific concrete actions, and the description would benefit from natural user language variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Figma designs, UI components, design systems, or needs to export assets from Figma'
Expand trigger terms to include natural variations users might say: 'UI design', 'mockups', 'design files', 'Figma frames', 'prototypes'
Make capabilities more concrete: instead of 'components', specify 'create and modify components, extract design tokens as CSS/JSON, export assets as PNG/SVG'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Figma) and lists several action areas (files, components, design tokens, comments, exports), but these are categories rather than specific concrete actions like 'extract design tokens' or 'add comments to frames'. | 2 / 3 |
Completeness | Describes what it does (automate Figma tasks) but has no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance for Claude, not selection criteria. | 1 / 3 |
Trigger Term Quality | Includes 'Figma' which is a strong natural keyword users would say, plus domain terms like 'components', 'design tokens', 'exports'. However, missing common variations like 'UI design', 'mockups', 'prototypes', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly targets Figma specifically via Rube MCP/Composio, which is a distinct niche. Unlikely to conflict with other skills due to the specific tool and platform combination. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent conciseness and actionability. The tool sequences, parameter documentation, and pitfall warnings provide concrete guidance. The main weakness is the lack of explicit validation checkpoints in workflows - there's no guidance on verifying successful operations or handling failures beyond noting what can go wrong.
Suggestions
Add explicit validation steps to workflows, e.g., 'Verify render succeeded by checking for null values in the URL map before proceeding to download'
Include error recovery guidance for common failures like 413 payload errors or 400 errors from unsupported file types
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Figma is or how APIs work. Every section provides actionable information without padding, and the quick reference table is an excellent token-efficient summary. | 3 / 3 |
Actionability | Provides specific tool names, exact parameter names, and concrete sequences. The pitfalls sections give precise details like node ID format conversion (dash to colon) and file type limitations that are immediately actionable. | 3 / 3 |
Workflow Clarity | Tool sequences are clearly numbered with prerequisites marked, but validation/verification steps are missing. For operations like exports or file modifications, there's no explicit 'verify success' or error recovery guidance beyond noting pitfalls. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from setup to workflows to quick reference. External link to Composio docs is one level deep. Content is appropriately structured for a skill of this scope without unnecessary splitting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.