CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figma-automation

Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/figma-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable MCP skill body: exact tool names, parameters, and error-recovery pitfalls throughout, with well-sequenced workflows and a clear setup validation flow. The main improvements are removing redundant sections (Known Pitfalls duplicates, the filler "When to Use") and splitting the Quick Reference into a separate file to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense operational data — exact tool slugs, parameters, and pitfalls — with zero explanation of concepts Claude already knows. Not 5 because the "Known Pitfalls" section repeats pitfalls already stated in workflow 1, the Quick Reference table re-lists every tool, and the "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview") is pure filler.

4 / 5

Actionability

Every workflow names exact MCP tool slugs (e.g. `FIGMA_GET_FILE_JSON`), concrete parameters (`ids` as comma-separated string, `simplify: True` for 70%+ size reduction), and actionable error remedies (413 → narrow scope or reduce depth; check `data_preview` if `data` is absent). This is fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Each workflow has a numbered tool sequence tagged [Prerequisite]/[Required]/[Optional] with a "When to use" clause, and the Setup section includes explicit validation (confirm connection ACTIVE before running). Not 5 because per-workflow validation checkpoints are only implicit via the pitfalls sections rather than explicit steps in the sequences (e.g., verify rendered URLs are non-null before downloading).

4 / 5

Progressive Disclosure

Well-organized single-file skill (no bundle files exist) with clear section headers, consistent per-workflow formatting, and a navigable Quick Reference table. Not 5 because at ~177 lines some content (the full Quick Reference table and detailed pitfalls) could live in a separate reference file, and the redundant "Known Pitfalls" and filler "When to Use" sections add navigation noise.

4 / 5

Total

17

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concrete, well-scoped description that clearly communicates the Figma automation domain and its capability areas with distinct trigger terms. Its main weakness is the missing "when to use" trigger guidance, which leaves completeness at the capped level.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to work with Figma files, extract design tokens, export design assets, or manage Figma comments."

Vary the action verbs to sharpen specificity, e.g. "Extract Figma file and component data, export/render nodes as images, extract design tokens to Tailwind, and manage comments and versions."

Include natural user phrasings like "export images", "render nodes", or "Figma URL" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports" names the domain plus several concrete capability areas. It falls short of 5 because the action verbs are collapsed into one generic "Automate" with an object list, and short of 3 because coverage spans more than 1-2 concrete actions with only minor gaps.

4 / 5

Completeness

The "what" is clear (automate Figma files, components, tokens, comments, exports) but there is no "Use when..." clause or equivalent trigger guidance; the second sentence ("Always search tools first for current schemas") is an instruction, not a when-clause, so completeness is capped at 3.

3 / 5

Trigger Term Quality

"Figma", "components", "design tokens", "comments", "exports" are natural terms users would say when needing this skill. Not 5 because common variations and phrases like "export images", "render", or "Figma URL" are missing; not 3 because keyword coverage goes well beyond a single generic term.

4 / 5

Distinctiveness Conflict Risk

"Figma" plus the specific "Rube MCP (Composio)" transport carves out a clear niche with distinct triggers and minimal overlap risk with other skills. No neighboring anchor fits better since the description is squarely domain-specific.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/figma-automation/SKILL.md

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.