CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-generate-library

Build or update a professional-grade design system library in Figma from a codebase. Useful for keeping the Figma source of truth in sync with shipped components.

52

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/figma-generate-library/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 tidy, well-structured catalogue entry that points clearly to its upstream source, but it offers little actionable guidance — the real workflow lives in the external repo rather than in the skill. Conciseness is good aside from a duplicated description.

Suggestions

Inline the core installation/invocation steps (e.g., the exact skills-directory path and clone command) instead of only opening the upstream URL, so the skill is actionable without an external round-trip.

Remove the verbatim repetition of the frontmatter description in the 'What it does' section to save tokens.

Tighten the workflow into explicit numbered steps with a verification checkpoint (e.g., confirm the skill appears in the agent's skill list before invoking).

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but the 'What it does' section repeats the frontmatter description verbatim, a minor redundancy that could be trimmed.

4 / 5

Actionability

Concrete guidance is minimal — the only executable command is 'open https://github.com/figma/skills', while the actual build/install workflow is delegated to the upstream repo with no specific steps inlined.

2 / 5

Workflow Clarity

A rough sequence is present (inspect upstream → install bundle → invoke by name/triggers), but the steps are vague on specifics such as where and how to install, with no checkpoints.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (What it does, Source, How to use) with a clearly signaled one-level external reference; no local bundle files exist, and the structure is appropriate for a short catalogue entry.

4 / 5

Total

13

/

20

Passed

Description

61%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 clearly states what the skill does and targets a distinct Figma niche, but it lacks an explicit 'Use when…' trigger clause, leaving the activation condition only weakly implied. Natural keyword coverage is good but not exhaustive.

Suggestions

Add an explicit 'Use when…' clause naming concrete trigger scenarios (e.g., 'Use when syncing Figma with shipped components or generating a design system library from code').

Expand the action list beyond 'Build or update' to name specific sub-tasks (e.g., extract components, map tokens, create Figma variables) for stronger specificity.

Include common synonyms/file terms users might say (e.g., 'Figma variables', 'design tokens', 'component library') to round out trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (Figma design system library) and two concrete actions ('Build or update'), but coverage is not comprehensive — it stops at build/update without detailing what the generation entails.

3 / 5

Completeness

The 'what' is clear ('Build or update a professional-grade design system library in Figma from a codebase'), but there is no explicit 'Use when…' trigger clause — only a weakly implying 'Useful for…' purpose statement, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say — 'design system library', 'Figma', 'codebase', 'sync' — giving good keyword coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The Figma design-system-library-from-codebase niche is mostly distinct with minimal conflict risk, though it could overlap slightly with general Figma 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.