CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-automation

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

59

Quality

68%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/figma-automation/SKILL.md

The canonical home for this skill is figma-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is a well-structured, actionable reference for Figma automation via Rube MCP, with clear tool sequences and parameter guidance. It is held back by duplicated pitfalls and the absence of explicit in-workflow validation/feedback loops.

Suggestions

Remove the duplicated "Known Pitfalls" section or fold it into the per-workflow pitfalls to reduce redundancy and improve conciseness.

Add explicit validation/feedback checkpoints in workflows involving batch or state-changing operations (e.g. verify render results for null IDs before downloading).

Add at least one example tool-call payload (e.g. a sample RUBE_SEARCH_TOOLS / FIGMA_GET_FILE_JSON invocation) to move actionability toward fully copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient with tool sequences, parameter tables, and pitfalls, but content is duplicated — the "Known Pitfalls" section repeats File Type Support and Node ID Formats already listed per-workflow, and the Quick Reference table re-lists tool slugs — so it could be tightened.

3 / 5

Actionability

Provides concrete, actionable guidance: exact tool slugs, parameter names and formats (e.g. "ids: Comma-separated node IDs (NOT an array)", "depth: 2"), and per-step [Required]/[Optional]/[Prerequisite] markers, with only minor gaps (no example tool-call payloads).

4 / 5

Workflow Clarity

Five workflows are clearly sequenced with numbered steps and prerequisite markers, and setup includes a checkpoint ("Confirm connection status shows ACTIVE before running any workflows"); validation/feedback loops within the workflows themselves are only implicit, leaving minor gaps.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference) with no nested references and all content appropriately inline; minor organization gaps (duplicated pitfalls) keep it just below a 5.

4 / 5

Total

15

/

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.

The description clearly states what the skill does and names distinct Figma capability areas, but it omits an explicit "Use when..." trigger clause, capping completeness. It is distinctive and reasonably specific.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to automate Figma files, components, design tokens, comments, or exports via Composio/Rube MCP."

Replace generic nouns ("files") with concrete verbs (e.g. "inspect files, extract components, pull design tokens") to lift specificity toward 5.

Include natural synonyms users say ("Figma", "design files", ".fig") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "files, components, design tokens, comments, exports" — giving clear coverage, though "files" is generic and the actions are stated as nouns rather than verbs, leaving minor gaps versus a fully comprehensive list.

4 / 5

Completeness

The "what" is clear ("Automate Figma tasks via Rube MCP ... files, components, design tokens, comments, exports") but there is no "Use when..." clause or equivalent explicit trigger guidance; "Always search tools first" is an instruction, not a when-condition, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("Figma tasks", "components", "design tokens", "comments", "exports"), with good keyword coverage; a few synonyms or surface variations are missing, so it stops short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Automate Figma tasks via Rube MCP (Composio)" carves out a clear niche with Figma-specific triggers and minimal overlap risk with other skills.

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.

Validation15 / 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
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.