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

58%

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

57%

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-organized catalogue pointer that cleanly delegates the full workflow to upstream, but it is light on actionable detail: the only command opens a URL, the install step lacks concrete commands, and the 'What it does' section redundantly restates the description.

Suggestions

Replace the description-verbatim 'What it does' block with skill-unique context or remove it to cut redundancy.

Provide a concrete install command (e.g., a git clone / copy into the skills directory) instead of sending the user to read the upstream README.

Add an explicit verification step confirming the skill is discoverable/invokeable after install.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids explaining concepts Claude knows, but the 'What it does' section repeats the frontmatter description verbatim and the blockquote ('Curated from Figma's MCP server guide') adds meta noise, so it could be tightened further.	2 / 3
Actionability	It offers a concrete command (`open https://github.com/figma/skills`) and a named invocation step, but the core task (running Figma Plugin API scripts) has no executable guidance and the install step is described without commands, so guidance is incomplete with key details missing.	2 / 3
Workflow Clarity	A sequence is present (inspect README → install bundle → invoke by name/trigger) but the install step is vague and there are no checkpoints or verification, matching 'steps listed but checkpoints missing or implicit.'	2 / 3
Progressive Disclosure	This is a sub-50-line pointer skill with clear sections (What it does, Source, How to use) and a single well-signaled one-level reference to the upstream repo; no nested local references exist, so well-organized sections earn the top score per the simple-skill note.	3 / 3
	Total	9 / 12 Passed

Description

60%

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 specific and third-person with a clear Figma niche, but lacks an explicit 'Use when...' trigger clause and uses somewhat technical terms, capping completeness and trigger-term quality at 2. Its self-declared prerequisite role also raises mild overlap risk with sibling Figma skills.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger situations (e.g., 'Use when the user wants to run or automate Figma Plugin API scripts, inspect a canvas, or manipulate Figma variables').

Soften the broad 'Prerequisite for every other Figma skill' framing or scope the triggers so this base skill does not compete with its sibling Figma skills.

Include more natural user-facing terms (e.g., 'Figma variables', 'Figma canvas', 'design tokens') alongside the API-level jargon.

Dimension	Reasoning	Score
Specificity	"canvas writes, inspections, variables, and design-system work" lists multiple concrete actions in third person ("Run Figma Plugin API scripts"), matching the anchor for multiple specific actions; not score 2 because it is comprehensive rather than naming only a partial set.	3 / 3
Completeness	It clearly states what ("Run Figma Plugin API scripts...") but lacks an explicit 'Use when...' trigger clause; the 'Prerequisite for every other Figma skill' line addresses ordering, not invocation intent, so per the guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains relevant terms ("Figma Plugin API scripts", "canvas", "design-system") but leans technical; missing common natural phrasings a user would say, so it lands on 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	It carves out a Figma niche but explicitly declares itself a prerequisite for 'every other Figma skill,' creating overlap with its sibling Figma skills, so it is somewhat specific but could still overlap rather than cleanly distinct.	2 / 3
	Total	9 / 12 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: f2760fd

Reviewed: about 14 hours 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.