understand-figma

Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./understand-anything-plugin/skills/understand-figma/SKILL.md

Quality

Content

92%

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 well-sequenced, concise, and actionable phased workflow with explicit validation checkpoints, but it offloads work to referenced scripts and an agent definition that are absent from the bundle, breaking its progressive-disclosure structure.

Suggestions

Ship the referenced bundle files (figma-scan.mjs, figma-merge.mjs under scripts/, agents/design-analyzer.md) so the one-level-deep references actually resolve.

Use explicit relative bundle paths (e.g. scripts/figma-scan.mjs) consistent with the references/ scripts/ assets/ convention rather than the unresolvable <SKILL_DIR> placeholder, and confirm each referenced path exists.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, giving concrete commands without explaining what Figma is or how libraries work; even the dense $UA_DIR resolution note earns its place by explaining a non-obvious fresh-shell constraint, matching the score-3 anchor.	3 / 3
Actionability	It provides concrete, copy-paste-ready commands (the core build step, 'node <SKILL_DIR>/figma-scan.mjs ...', the find-based cleanup) with explicit argument passing, matching the score-3 anchor of fully executable guidance rather than vague direction.	3 / 3
Workflow Clarity	Phases 0-4 form a clear sequence with explicit checkpoints: non-zero scan exit -> relay stderr and STOP, UP_TO_DATE -> STOP, and merge validation via mergeDesignGraph, matching the score-3 anchor of a clear sequence with explicit validation steps.	3 / 3
Progressive Disclosure	The SKILL.md is intentionally lean and references scripts for the heavy lifting, but the referenced bundle files (figma-scan.mjs, figma-merge.mjs, agents/design-analyzer.md) do not exist in the bundle, so the one-level-deep navigation does not actually resolve, fitting score 2 over score 3.	2 / 3
	Total	11 / 12 Passed

Description

67%

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 occupies a clearly distinct Figma niche, but it omits an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrasing, capping completeness and trigger quality at the mid level.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user shares a Figma file or link and wants a navigable design graph / component inventory.'

Soften jargon in the trigger phrasing by including user-level terms like 'Figma designs', 'Figma link', and 'design system inventory' alongside the technical enumerations.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions and outputs: 'Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens)', matching the score-3 anchor of enumerating several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly answers 'what' the skill does but has no 'Use when...' or equivalent explicit trigger guidance, so per the rubric guideline a missing trigger clause caps completeness at 2 (has what, when only implied).	2 / 3
Trigger Term Quality	Natural terms like 'Figma file' and 'design' are present, but coverage leans on jargon ('component sets', 'instances', 'design tokens', "kind:\"design\" dashboard") and omits common user variations, fitting score 2 rather than the broad natural-term coverage of score 3.	2 / 3
Distinctiveness Conflict Risk	The Figma-specific niche and prominent 'Figma' terminology make it clearly distinguishable and unlikely to trigger for the wrong skill, matching the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	10 / 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: Egonex-AI/Understand-Anything
Path: understand-anything-plugin/skills/understand-figma/SKILL.md
Commit: 6ae7187

Reviewed: 4 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.