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).
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is an excellent skill description that clearly defines its capabilities, provides natural trigger terms, explicitly states when to use it, and proactively distinguishes itself from a closely related skill. The inclusion of a 'Do NOT use' clause is particularly effective for disambiguation in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'fetch design context, screenshots, variables, and assets from Figma', 'translate Figma nodes into production code', and 'Figma MCP setup and troubleshooting'. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (fetch design context, screenshots, variables, assets; translate nodes to code) and 'when' ('Use when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup'). Also includes an explicit negative boundary ('Do NOT use when...') which further clarifies usage. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Figma URLs', 'node IDs', 'design-to-code', 'Figma MCP', 'screenshots', 'variables', 'assets'. These cover the natural language a user would use when requesting Figma-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from a related skill ('figma-implement-design') by defining a clear boundary: general Figma data fetching vs. pixel-perfect code implementation. This negative trigger clause significantly reduces conflict risk with the sibling skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that clearly defines the Figma MCP workflow with good sequencing and validation steps. Its main weakness is the lack of concrete executable examples (e.g., actual tool call syntax with parameters) and some minor redundancy in the implementation rules. The progressive disclosure and workflow clarity are strong, with appropriate delegation to reference files.
Suggestions
Add concrete tool call examples with actual parameters, e.g., showing the exact syntax for get_design_context with a sample node ID or URL
Remove the duplicate 'validate against Figma' instruction that appears in both the required flow (step 6) and implementation rules (last bullet) to improve conciseness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy—e.g., 'Validate against Figma for 1:1 look and behavior' appears in both the required flow and implementation rules. Some bullet points like 'Treat the Figma MCP output as a representation of design and behavior, not as final code style' could be tightened. However, it avoids explaining what Figma or MCP is, which is good. | 2 / 3 |
Actionability | The required flow provides a clear sequence of tool calls (get_design_context, get_metadata, get_screenshot), which is concrete. However, there are no executable code examples, no exact command syntax or parameters for these tool calls, and the implementation rules are more principle-based than copy-paste actionable. The guidance is specific enough to follow but lacks the concrete examples that would earn a 3. | 2 / 3 |
Workflow Clarity | The required flow is clearly sequenced with numbered steps, includes a fallback/recovery path (step 2 for truncated responses), has explicit ordering constraints ('Only after you have both...'), and includes validation checkpoints (step 6). The 'do not skip' annotation reinforces the importance of following the sequence. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to figma-mcp-config.md for setup/debugging and figma-tools-and-prompts.md for tool catalog and prompts. The main content stays focused on workflow and rules while appropriately delegating detailed reference material to separate files. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- tech-leads-club/agent-skills
- Commit
906a57d
- 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.