CtrlK
BlogDocsLog inGet started
Tessl Logo

figma

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Use when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting. Covers general Figma data fetching and exploration. Do NOT use when the goal is specifically pixel-perfect code implementation from a Figma design (use figma-implement-design instead).

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, actionable skill body with a clear validated workflow and clean progressive disclosure into two reference files. The only real improvement space is trimming minor redundancy and adding a concrete code/tool-call example block.

Suggestions

Consolidate the three 'IMPORTANT' asset-handling bullets into a single concise rule to tighten conciseness.

Add one short example showing the exact MCP tool-call sequence (get_design_context -> get_screenshot -> implementation) to push actionability to anchor 5.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's competence without explaining what Figma is, but the three overlapping 'IMPORTANT' asset-handling bullets and some restated rules keep it just shy of the lean anchor 5.

4 / 5

Actionability

Concrete, specific MCP tool calls (get_design_context, get_metadata, get_screenshot) with an explicit ordered flow are highly actionable, but there is no literal executable code/command block, leaving a minor gap versus anchor 5.

4 / 5

Workflow Clarity

A numbered 'Required flow (do not skip)' sequence includes an explicit validation checkpoint (step 6: 'Validate against Figma for 1:1 look and behavior') and a feedback loop (step 2: if truncated, get_metadata then re-fetch), matching the anchor 5 example.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview that offloads setup/debugging and the tool catalog to two real, one-level-deep reference files, both clearly signaled inline and in a References section.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong description that concretely states capabilities, gives explicit trigger conditions, and cleanly separates itself from a sibling skill. The main weakness is the imperative/second-person voice, which costs a specificity point.

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. 'Fetches design context, screenshots, variables, and assets from Figma and translates Figma nodes into production code.'

Add a few more natural user-facing synonyms (e.g. 'Figma file', 'Figma link') to lift trigger term coverage toward anchor 5.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'fetch design context, screenshots, variables, and assets' and 'translate Figma nodes into production code' — which meets the comprehensive anchor 5, but the imperative 'Use the Figma MCP server...' voice triggers the second-person specificity penalty (-1).

4 / 5

Completeness

Explicitly answers both what (fetch context/screenshots/variables/assets, translate nodes to code) and when ('Use when a task involves Figma URLs, node IDs, design-to-code implementation...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ('Figma URLs, node IDs, design-to-code implementation, Figma MCP setup and troubleshooting') but stops short of anchor 5 by omitting common synonyms/variations a user might say.

4 / 5

Distinctiveness Conflict Risk

Clear niche with an explicit boundary clause ('Do NOT use when... use figma-implement-design instead') minimizing conflict with the related skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-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.