CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-design

Figma design-to-code workflows, design token extraction, component inspection, and asset export. Use when translating Figma designs into code, extracting design tokens, or referencing component specs.

77

Quality

96%

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

100%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 tight, well-structured skill body: concrete tool calls, an explicit acceptance-gated workflow with a retry loop, and a practical non-obvious mapping table. No bundle files exist, but the body is appropriately self-contained for its scope.

DimensionReasoningScore

Conciseness

Lean body with a tool table, a numbered workflow, and a mapping table — no padding or explanation of concepts Claude already knows, and every line (e.g. the 'Never call get_file without depth' warning) earns its place.

5 / 5

Actionability

Provides concrete MCP tool names with their parameters, specific file targets ('src/styles/tokens.css'), a data-testid verification hook, and exact CSS mappings (e.g. 'Hug contents' -> 'width: fit-content') — copy-paste-ready guidance for the common cases.

5 / 5

Workflow Clarity

A five-step numbered sequence with explicit acceptance criteria ('spacing within 4px, token colors exact, font family and weight exact') and a feedback loop in step 5 ('Outside threshold -> fix the token mapping or ask design; re-run from step 1').

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files in references/scripts/assets, and the content is organized into clearly headed sections (MCP tools, Workflow, Figma -> CSS mappings); per the simple-skill exception this earns a 5 with no external references needed.

5 / 5

Total

20

/

20

Passed

Description

92%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, concise description that pairs four concrete capabilities with an explicit 'Use when' trigger clause and Figma-bound language. Trigger-term coverage is the only slight gap, missing a few natural synonyms.

Suggestions

Consider adding natural synonyms such as 'design handoff' or 'design system' to broaden trigger-term coverage.

Mentioning the Figma API or file-key concept in the description could help users searching for Figma-integration triggers find this skill.

DimensionReasoningScore

Specificity

Lists four concrete actions — 'design-to-code workflows, design token extraction, component inspection, and asset export' — giving comprehensive coverage of what the skill does, matching the 5 anchor's multiple-specific-actions bar.

5 / 5

Completeness

Explicitly answers both 'what' (the four capabilities) and 'when' via a concrete 'Use when translating Figma designs into code, extracting design tokens, or referencing component specs' trigger clause.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('translating Figma designs into code', 'extracting design tokens', 'referencing component specs'), but a few natural synonyms like 'design handoff' or 'design system' are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Figma-specific niche with distinct, domain-bound triggers ('Figma designs', 'design tokens', 'component specs') makes overlap with other skills minimal.

5 / 5

Total

19

/

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
monkilabs/opencastle
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.