Tessl • The package manager for agent skills

SkillPublic

figma-create-design-system-rules

Generate project-specific design system rules for Figma-to-code workflows. Useful for capturing tokens, naming, and lint rules in one source.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/figma-create-design-system-rules/SKILL.md

Quality

Content

43%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-sectioned catalogue stub, but it provides almost no actionable guidance: the real workflow lives entirely in an upstream GitHub repo and the single instruction reduces to "go inspect the upstream README". As a SKILL.md it reads as an advertisement rather than an executable skill, leaving both actionability and workflow clarity well below par.

Suggestions

Replace the `open https://github.com/figma/skills` placeholder with a concrete, executable install step (e.g., a git clone or copy command with the exact target path in the agent's skills directory).

Inline or bundle the core workflow (how to generate the design system rules: what inputs to read from Figma, what rule format to emit, where to write it) in SKILL.md or a clearly referenced one-level-deep file, instead of deferring all content to an external repo.

Add a short verification step so the agent can confirm the skill is installed and invocable (e.g., check the trigger phrases resolve to the installed bundle) before telling the user it is ready.

Dimension	Reasoning	Score
Conciseness	The body is short and lean with no explanation of concepts Claude already knows, matching anchor 4 (efficient with minor trimming possible). It is not a 5 because the frontmatter description is repeated verbatim in "What it does" and source/category data from the frontmatter is restated in the body.	4 / 5
Actionability	The only "command" is `open https://github.com/figma/skills` alongside "Inspect the upstream README for exact paths" — a high-level hint with no concrete install command or executable steps, matching anchor 2. It is not 3 because there is no partially-executable guidance, just a pointer to go read an external README.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream, install the bundle, invoke by name or trigger), but the critical install step is entirely undefined and there are no checkpoints, matching anchor 2. It does not reach 3 because the listed steps have a major gap rather than merely missing validation, and the simple-skill exception does not apply since the single action (installing and running the skill) is ambiguous.	2 / 5
Progressive Disclosure	No bundle files (references/, scripts/, assets/) exist, and the sections are clearly labeled, but the actual skill content lives in an out-of-band GitHub URL rather than clearly signaled, one-level-deep reference files — matching anchor 3 (some structure but could be better organized). It is not 4/5 because the substantive content the skill advertises is not present or navigable locally.	3 / 5
	Total	11 / 20 Passed

Description

66%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 is concise and specific about what the skill produces, with a clear niche and mostly natural trigger keywords. Its main weakness is the absence of an explicit "Use when..." trigger clause, which both caps completeness and leaves the "when" only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Figma-to-code workflows, design system rules, or wants to capture Figma tokens, naming, or lint rules in one place."

Broaden natural keyword coverage with common synonyms users would say, such as "Figma", "design tokens", or "component library", to strengthen trigger term quality and distinctiveness.

State a couple of concrete downstream actions (e.g., generating rules the agent applies when converting Figma designs to code) to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Generate project-specific design system rules for Figma-to-code workflows" and "capturing tokens, naming, and lint rules" name the domain plus several concrete artifacts, matching anchor 4 (several specific actions, minor coverage gaps). It falls short of 5 because it does not comprehensively cover the actions involved (e.g., applying or validating the generated rules).	4 / 5
Completeness	The "what" is clear (generate design system rules capturing tokens, naming, and lint rules), but there is no "Use when..." clause; "Useful for capturing..." only weakly implies the "when". Per the judging guideline, a missing explicit trigger guidance caps completeness at 3, and it does not reach 4 because the "when" is not present even imprecisely.	3 / 5
Trigger Term Quality	The description includes good natural keywords ("design system rules", "Figma-to-code", "tokens", "lint rules") that users would plausibly say, but misses common variations and synonyms such as "Figma" alone, "design tokens", or "component library". This matches anchor 4 (good keyword coverage, a few natural terms missing) rather than 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	The Figma-to-code design system rules niche is clear and distinct, with only minor overlap risk against closely related generic design-system or styling skills. It is not a 5 because "design system rules" and "tokens" could still collide with general design-tokens or theming skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/figma-create-design-system-rules/SKILL.md
Revision: 78d5637

Reviewed: 17 days ago

Discovery Implementation Validation

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.

figma-create-design-system-rules

Table of Contents

Is this your skill?