Name: figma-generate-diagram
Rating: 94.6 (1 reviews)
Author: figma

figma-generate-diagram

MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).

1.51x

Quality

93%

Does it follow best practices?

Impact

97%

1.51x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

92%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, highly actionable routing skill with clear sequencing, real validation feedback loops, and excellent progressive disclosure via verified one-level references. The only weakness is mild verbosity in the context-gathering section and some repeated cross-references.

Suggestions

Tighten Step 4 ('Garbage in, garbage out'): collapse the bulleted source list into a shorter inline form or move the longer enumeration into a reference file, keeping only the 'don't hallucinate / flag gaps' rule inline.

Consolidate the repeated hybrid-workflow pointer (Steps 3.7, 3.8, 5, and 7) so it is introduced once in Step 5 and merely referenced by short link elsewhere, reducing token cost.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of explanations Claude already knows, but Step 4's context-gathering source list runs long and the hybrid-workflow pointer is repeated across Steps 3, 5, and 7 — minor instances that could be trimmed.	4 / 5
Actionability	Fully executable guidance: a routing table mapping intent to type and reference file, exact universal constraints with syntax examples (A["Process (main)"], -->\|"O(1) lookup"\|), a reserved-words list, and explicit Step 6 tool parameters with required/optional distinction.	5 / 5
Workflow Clarity	A clear 7-step sequence with explicit feedback loops (2-attempt regeneration cap, 'stop and ask what's wrong') and pre-generation validation (asking focused questions when context is thin).	5 / 5
Progressive Disclosure	A lean overview that routes to one-level-deep, clearly-signaled reference files (architecture, flowchart, sequence, erd, state, gantt, workflow — all verified present), with per-type detail correctly split out of SKILL.md.	5 / 5
	Total	19 / 20 Passed

Description

95%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, trigger-rich description that clearly defines its niche as a mandatory prerequisite for Mermaid→FigJam diagram generation and is unlikely to fire for the wrong skill. The only gap is a slight lack of emphasis on the core generation action itself.

Dimension	Reasoning	Score
Specificity	Names the diagram-generation domain and several concrete actions ('Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely'), but the framing emphasizes routing/gating rather than the direct generation action itself, leaving minor coverage gaps short of a 5.	4 / 5
Completeness	Explicitly answers both 'what' (routes, sets constraints, advises when to skip) and 'when' ('Trigger whenever the user asks to create, generate, draw...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms ('create, generate, draw, render, sketch, or build'), many diagram-type names (flowchart, sequence, ERD, state, gantt, timeline), plus Mermaid and FigJam — few natural phrases are missing.	5 / 5
Distinctiveness Conflict Risk	Tightly scoped to the generate_diagram tool and Mermaid→FigJam diagrams, with explicit skip boundaries (mindmaps, pie charts, class diagrams), giving a clear niche with minimal conflict risk.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: figma/mcp-server-guide
Path: skills/figma-generate-diagram/SKILL.md
Commit: 72fcf1f

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.