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. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

95

2.12x
Quality

92%

Does it follow best practices?

Impact

100%

2.12x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 sequenced workflow and clean progressive disclosure to real reference files. The main weakness is mild redundancy between the required-flow steps and the implementation-rules bullets.

Suggestions

De-duplicate guidance that appears in both 'Required flow' and 'Implementation rules' (e.g., translate-to-conventions and validate-against-Figma) so each rule lives in one place and the body tightens toward a 3 on conciseness.

Consider merging the 'Implementation rules' bullets that restate flow steps into a single source of truth, keeping the numbered flow as the spine.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept-explaining padding, but the 'Required flow' and 'Implementation rules' overlap — translate-to-conventions and validate-against-Figma each appear in both sections — so it could be tightened rather than every token earning its place.

2 / 3

Actionability

Names concrete MCP tools (get_design_context, get_metadata, get_screenshot) with precise directives and exact asset-handling rules; for an instruction-only skill the guidance is concrete and specific rather than abstract.

3 / 3

Workflow Clarity

A clearly numbered six-step flow with explicit ordering ('do not skip', 'Only after you have both'), a re-fetch feedback loop for truncation, and an explicit validation checkpoint before marking complete.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that signals two real, one-level-deep reference files (figma-mcp-config.md, figma-tools-and-prompts.md) with one-line descriptions in a References section for easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description with explicit trigger guidance and a clear niche, written in the correct third-person voice. It cleanly answers both what and when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'fetch design context, screenshots, variables, and assets' and 'translate Figma nodes into production code' — matching the anchor for several specific concrete actions rather than just naming a domain.

3 / 3

Completeness

Explicitly answers both what it does (fetch/translate) and when to use it via the 'Trigger when...' clause, so it is not merely implied as in the score-2 anchor.

3 / 3

Trigger Term Quality

'Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting' covers natural terms a user would say, though it leans heavily on the Figma keyword rather than varied phrasings.

3 / 3

Distinctiveness Conflict Risk

The Figma MCP niche with triggers tied to Figma URLs and node IDs is distinct and unlikely to conflict with unrelated skills.

3 / 3

Total

12

/

12

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