CtrlK
BlogDocsLog inGet started
Tessl Logo

od-figma-migration

Default reference pipeline for the figma-migration taskKind — figma-extract → token-map → generate → critique.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/scenarios/od-figma-migration/SKILL.md
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.

The body is a lean, well-structured reference: a concrete pipeline config with an explicit critique feedback loop and specific GenUI surface requirements. It assumes Claude's competence and earns its tokens, with only minor conciseness and actionability refinements available.

DimensionReasoningScore

Conciseness

The body is efficient and free of generic concept explanations, with only minor prose (the sequencing rationale and spec citations) that could be trimmed slightly.

4 / 5

Actionability

It provides a concrete, copy-ready pipeline config (jsonc) and specific GenUI surface parameters (oauth.route='connector', connectorId='figma', kind='form'), with only minor gaps in executable detail.

4 / 5

Workflow Clarity

The pipeline is explicitly sequenced via the stages array and includes an explicit validation feedback loop — the critique stage repeats until 'critique.score>=4 || iterations>=3'.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external bundle files and no need for them; content is well-organized under clear section headers, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

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

The description gives a clear, fairly specific statement of what the skill does but omits any explicit trigger guidance for when Claude should invoke it. Adding a 'Use when...' clause with natural user phrases would raise the completeness and trigger-term dimensions.

Suggestions

Append an explicit 'Use when...' clause naming natural user triggers (e.g. 'Use when migrating a Figma design to code or generating HTML from Figma files').

Replace or gloss the internal term 'taskKind' with language a user would actually say.

Add common synonyms or file references (Figma, Figma URLs, design-to-code) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (figma-migration) and lists several concrete stages — figma-extract, token-map, generate, critique — via an explicit arrow chain, with only minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does (the default reference pipeline and its stages) but provides no 'Use when...' clause, so the 'when' is missing — capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'figma-migration' and 'figma' are reasonably natural terms a user might say, but 'taskKind' is internal jargon and common synonyms or variations are missing.

3 / 5

Distinctiveness Conflict Risk

The figma-migration niche is specific and mostly distinct, with only minor overlap risk against other Figma-related skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.