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).

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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-organized, instruction-style skill: an explicit ordered workflow with a validation checkpoint, concrete tool calls and rules, and clean one-level references that exist on disk. It assumes Claude's intelligence and stays tight. Strong result with no material weaknesses.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explanation of what Figma/MCP is), and every section carries concrete rules; only minor throat-clearing in the intro/meta sentence keeps it just at the efficient top anchor.

3 / 3

Actionability

Gives concrete, executable guidance naming specific MCP tools (get_design_context, get_metadata, get_screenshot) and explicit rules ("DO NOT import/add new icon packages", "Replace Tailwind utility classes with the project's preferred tokens"); absence of raw code is fine for this instruction-only skill.

3 / 3

Workflow Clarity

A clearly numbered "Required flow (do not skip)" with a truncation fallback loop (get_metadata then re-fetch) and a validation checkpoint ("Validate against Figma for 1:1 look and behavior before marking complete"), matching the explicit-validation-with-feedback anchor.

3 / 3

Progressive Disclosure

A concise overview signals two real one-level-deep references (figma-mcp-config.md and figma-tools-and-prompts.md), both present on disk and restated in a References section, with no nested/inline walls of text.

3 / 3

Total

12

/

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.

The description is specific, complete, and distinctive: it names concrete Figma MCP actions, gives explicit Use-when triggers, and adds a Do-NOT-use exclusion to avoid overlapping with a sibling skill. It is concise and free of fluff. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "fetch design context, screenshots, variables, and assets" and "translate Figma nodes into production code" — rather than vague domain references, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers what (fetch/translate actions) and when ("Use when a task involves..."), plus a "Do NOT use when..." exclusion, satisfying the explicit-trigger top anchor.

3 / 3

Trigger Term Quality

Covers natural phrases users would say ("Figma URLs", "design-to-code implementation", "Figma MCP setup and troubleshooting", "pixel-perfect code"), giving good natural-term coverage.

3 / 3

Distinctiveness Conflict Risk

Has a clear Figma-MCP niche with distinct triggers and an explicit disambiguation pointing to figma-implement-design, making wrong-skill triggering unlikely.

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