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

55%

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

40%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 body is a thin catalogue entry pointing to an upstream bundle; it is reasonably structured but offers little concrete, executable guidance and an undefined install workflow. Its main weakness is actionability, since the actual task is deferred to upstream with only high-level hints locally.

Suggestions

Replace the macOS-only `open https://...` with portable, concrete steps (e.g. `git clone` the repo and copy the skill folder into the agent skills directory) so the install workflow is executable.

Drop the duplicate "What it does" section and trim the Open Design/planning meta-prose to tighten token efficiency.

Add an explicit invocation example showing the trigger phrase or `figma-create-new-file` call so the final step is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is short, but the "What it does" section repeats the frontmatter description verbatim and the "How to use" prose explains catalogue/planning mechanics Claude does not need, so it is mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Guidance is high-level ("install the upstream bundle", "ask the agent to invoke this skill"), and the only concrete command (`open https://github.com/figma/skills`) just inspects a README and is not portable, leaving the specific executable steps missing.	2 / 5
Workflow Clarity	A rough sequence is implied (install bundle -> inspect README -> invoke by name/trigger), but the install step is undefined and no concrete sub-steps are given, matching the rough-sequence-with-many-gaps anchor.	2 / 5
Progressive Disclosure	The body is well organized into clear sections with a single one-level-deep external reference (the upstream repo URL) that is clearly signaled; it stops short of a 5 only because the skill is essentially a stub pointer with no content split to navigate.	4 / 5
	Total	11 / 20 Passed

Description

70%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 third-person, specific to its Figma niche, and answers both what and when, with good natural trigger terms. Its main limitation is that it describes a single simple action and the when-clause is softly phrased.

Suggestions

Make the when-clause more directive, e.g. "Use when starting a scripted design-system build or a FigJam workshop and no file exists yet."

Add a natural synonym or two (e.g. "new Figma doc", "blank canvas") to broaden trigger coverage.

Confirm the action scope is comprehensive (e.g. does it also set a default page size or template?) so specificity can reach a higher anchor.

Dimension	Reasoning	Score
Specificity	It names the domain ("Figma Design or FigJam file") and one concrete action ("Create a new blank ... file"), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states a clear "what" (create a new blank file) and an explicit "when" ("Useful as the first step in scripted design-system or workshop workflows"), but the when could be more directive/specific, matching the anchor for both present with room to sharpen.	4 / 5
Trigger Term Quality	Natural terms a user would say are present ("Figma Design", "FigJam", "new ... file", "create"), giving good keyword coverage, though a few synonyms or file extensions are missing so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	It is clearly Figma-specific with a distinct niche (new file creation), carrying only minor overlap risk with closely related Figma skills rather than the minimal-conflict clarity of a 5.	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-new-file/SKILL.md
Commit: 1a7a23d

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