figma-use

Run Figma Plugin API scripts for canvas writes, inspections, variables, and design-system work. Prerequisite for every other Figma skill in this catalogue.

Quality

53%

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-use/SKILL.md

Quality

Content

47%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 skill is a thin, well-structured catalogue entry that points to an upstream bundle, but it offers little executable guidance: the single real command opens a URL and the actual install step is left vague. Workflow sequence is rough and lacks checkpoints.

Suggestions

Replace the generic `open https://github.com/figma/skills` with the concrete install step (e.g. the exact skills-directory path and the clone/copy commands) so the core action is executable.

Remove the verbatim duplication of the frontmatter description in the "What it does" section, or make it add new information.

Number the How-to-use steps explicitly (1. locate upstream paths, 2. install bundle into <skills dir>, 3. invoke via `figma-use` or a trigger) so the sequence and its checkpoints are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean at ~30 lines and assumes competence, but the "What it does" section duplicates the frontmatter description verbatim and the catalogue-mechanism explanation adds minor over-explanation.	4 / 5
Actionability	Only one concrete command is given (`open https://github.com/figma/skills`); the core workflow step ("install the upstream bundle into your active agent's skills directory") is a high-level hint with no specific executable steps.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream -> install bundle -> invoke by name), but the central install step is undefined (no skills-directory path or command) and there are no checkpoints or validation.	2 / 5
Progressive Disclosure	Clean, well-organized sections with a clearly signaled one-level-deep upstream reference, but navigation only points to a generic repo URL with a comment to "Inspect the upstream README for exact paths" rather than specific files.	4 / 5
	Total	12 / 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 states concrete capabilities clearly but omits any explicit "when to use it" guidance, and its trigger terms skew toward technical API phrasing rather than natural user language. It is distinctive within a Figma niche but carries some family-overlap risk from its prerequisite framing.

Suggestions

Add an explicit 'Use when ...' clause with natural trigger phrases (e.g. 'Use when you need to automate Figma canvas edits, inspect a file, or manipulate variables and design tokens').

Soften the 'Prerequisite for every other Figma skill' framing or move it out of the description so the trigger surface stays unambiguous against sibling Figma skills.

Include a common natural synonym (e.g. 'Figma plugin' or 'automate Figma') alongside 'Figma Plugin API' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete action categories ("canvas writes, inspections, variables, and design-system work") rather than vague language, but they are categories rather than fully concrete operations, leaving minor coverage gaps.	4 / 5
Completeness	The "what" is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance; "Prerequisite for every other Figma skill" is contextual positioning, not a when, so completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant keywords appear ("Figma", "canvas", "variables", "design-system work"), but "Figma Plugin API" leans technical and common natural phrasings a user would say (e.g. "edit Figma", "Figma plugin") are missing.	3 / 5
Distinctiveness Conflict Risk	It occupies a clear Figma niche with distinct API/canvas/variables triggers, but the "Prerequisite for every other Figma skill in this catalogue" framing creates minor overlap risk with the related Figma skill family.	4 / 5
	Total	14 / 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-use/SKILL.md
Commit: 1a7a23d

Reviewed: 3 days ago

Table of Contents

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.