figma-create-new-file

Create a new blank Figma Design or FigJam file. Useful as the first step in scripted design-system or workshop workflows.

Quality

57%

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-new-file/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 well-structured and appropriately lean for a simple catalogue entry, with clean progressive disclosure and a single external reference. Its weaknesses are redundant content that duplicates the frontmatter and a vague install step that leaves the core action under-specified.

Suggestions

Replace the verbatim 'What it does' repeat and the 'Source' section (which duplicates frontmatter) with content that adds new information, or remove them to tighten the body.

Make the install step concrete: give the actual commands or paths for copying the upstream bundle into the agent's skills directory instead of describing it abstractly.

Clarify the workflow by numbering the steps (inspect README -> install bundle -> invoke by name/trigger) so the sequence and its checkpoints are explicit.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean, but 'What it does' repeats the frontmatter description verbatim and the 'Source' section restates upstream/category already in the frontmatter, so it could be tightened — matching 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	It offers one concrete command ('open https://github.com/figma/skills') but the core instruction to 'install the upstream bundle into your active agent's skills directory' lacks concrete commands or paths, fitting 'some concrete guidance but incomplete; missing key details'.	2 / 3
Workflow Clarity	A sequence is present (advertise in Open Design, inspect upstream README, install bundle, invoke by name/trigger), but the install step is vague and checkpoints are only implicit, matching 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	The body is under 50 lines with well-organized sections and no local bundle files to navigate, and it appropriately points to a single external upstream URL rather than nesting local references, matching the 'well-organized sections' allowance for simple skills.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 clear and specific about creating new Figma/FigJam files with a distinct niche, but it only implies when to use it rather than giving explicit trigger guidance and offers just one concrete action. Adding an explicit 'Use when...' clause and a broader spread of natural trigger terms would raise completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants a fresh Figma Design or FigJam canvas to start a new design-system or workshop session.'

Broaden natural trigger terms in the description (e.g., 'new Figma file', 'start a FigJam', 'blank Figma canvas') so coverage matches how users actually phrase the request.

Optionally mention a second concrete capability (e.g., choosing Design vs FigJam type) to lift specificity toward level 3.

Dimension	Reasoning	Score
Specificity	It names one concrete action ('Create a new blank Figma Design or FigJam file') in a clear domain, but does not enumerate multiple distinct actions, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It clearly answers 'what' (create a new blank Figma/FigJam file), but the 'when' is only implied via 'Useful as the first step in scripted design-system or workshop workflows' with no explicit 'Use when...' clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Terms like 'Figma Design', 'FigJam file', 'design-system', and 'workshop workflows' are relevant, but the phrasing leans on workflow jargon and misses common natural variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Creating a new blank Figma Design or FigJam file is a narrow, clearly scoped niche with distinct triggers that is unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 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-create-new-file/SKILL.md
Commit: f2760fd

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