CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-generative-plugins

**MANDATORY prerequisite** — load this skill before calling `create_generative_plugin` or `update_generative_plugin`. Use when the user asks to create, author, change, fix, or extend a reusable generative Figma plugin.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured, actionable orchestration guide that keeps the overview lean and delegates detailed authoring to a clearly signaled single reference. The main improvement room is making a few implicit validation checkpoints explicit.

Suggestions

Add an explicit 'verify the scaffold state' checkpoint between reading source URIs and replacing files in the create workflow.

Include one complete worked update_generative_plugin call (a small files array literal) inline so the common case is copy-paste ready without opening the reference.

Collapse the line-9 prerequisite restatement and line-28 reinforcement into a single statement to remove the minor redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept padding, but has minor redundancy such as the prerequisite restatement (line 9) and the 'Never stop after create' reinforcement (line 28).

4 / 5

Actionability

Concrete tool names, exact argument shapes ({ path: 'code.ts', content: '...' }, planKey, commitMessage, metadata), and a copy-paste-ready completion URL; minor gaps remain since no full worked update call is shown inline (delegated to the reference).

4 / 5

Workflow Clarity

Two clearly sequenced numbered workflows with an explicit build-error retry-once feedback loop, preflight checks, and 'read every source URI' verification; minor validation checkpoints are implicit rather than explicit.

4 / 5

Progressive Disclosure

A concise overview body points to a single one-level-deep reference (references/authoring.md, 246 lines, only in-page anchor links) whose contents are enumerated, with its own table of contents for navigation.

5 / 5

Total

17

/

20

Passed

Description

83%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.

A strong, specific description with an explicit trigger clause and a clearly scoped niche. Its only weakness is that the capability is stated indirectly as a mandatory prerequisite rather than as a direct 'what does this do' statement.

Suggestions

Lead with a direct capability statement (e.g., 'Creates and updates reusable generative Figma plugins') before the prerequisite clause, so the 'what' is explicit.

Add natural synonyms such as 'edit', 'build', or 'make' alongside 'create, author, change, fix, extend' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the concrete tool calls (create_generative_plugin, update_generative_plugin) and five concrete lifecycle verbs (create, author, change, fix, extend), giving comprehensive coverage of the skill's actions.

5 / 5

Completeness

The 'when' is explicit ('Use when the user asks to create, author, change, fix, or extend...') and the 'what' is present, but the capability is framed indirectly as a prerequisite rather than a direct statement of what the skill does.

4 / 5

Trigger Term Quality

Natural user phrases are present ('create...Figma plugin', 'fix...plugin', 'extend'), but 'author' leans technical and common synonyms like edit/build/make are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (reusable generative Figma plugins via named MCP tools) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
figma/mcp-server-guide
Reviewed

Table of Contents

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.