Generate Excalidraw diagrams from natural language descriptions. Outputs .excalidraw JSON files openable in Excalidraw. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", "generate an Excalidraw file", "draw an ER diagram", "create a sequence diagram", or "make a class diagram". Supports flowcharts, relationship diagrams, mind maps, architecture, DFD, swimlane, class, sequence, and ER diagrams. Can use icon libraries (AWS, GCP, etc.) when set up. Do NOT use for code architecture analysis (use the architecture skills), Mermaid diagram rendering (use mermaid-studio), or non-visual documentation (use docs-writer).
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, extensive natural trigger terms, clear 'Use when' guidance, and explicit disambiguation from related skills. The inclusion of 'Do NOT use' clauses with alternative skill references is particularly strong for reducing conflict risk in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generate Excalidraw diagrams, output .excalidraw JSON files, supports flowcharts, relationship diagrams, mind maps, architecture, DFD, swimlane, class, sequence, and ER diagrams. Also mentions icon library support. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate Excalidraw diagrams, output .excalidraw JSON files, supports various diagram types) and 'when' (explicit 'Use when' clause with extensive trigger phrases). Also includes explicit 'Do NOT use' guidance for disambiguation, which goes above and beyond. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create a diagram', 'make a flowchart', 'visualize a process', 'draw a system architecture', 'create a mind map', 'generate an Excalidraw file', 'draw an ER diagram', 'create a sequence diagram', 'make a class diagram'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit negative boundaries ('Do NOT use for code architecture analysis, Mermaid diagram rendering, or non-visual documentation') and references to alternative skills. The Excalidraw-specific focus and file format (.excalidraw JSON) create a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive skill that provides excellent actionable guidance for generating Excalidraw diagrams. Its main strength is the concrete JSON examples, detailed validation checklist, and well-organized progressive disclosure to reference files. Its primary weakness is some redundancy across sections (element ordering, common mistakes, and validation checklist overlap), which could be tightened to save tokens.
Suggestions
Consolidate the overlapping content between 'Common Mistakes to Avoid', 'Validation Checklist', and 'Troubleshooting' sections — many items appear in all three. A single authoritative checklist with the mistakes integrated would be more token-efficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) with some redundancy — spacing guidelines, element ordering rules, and common mistakes are repeated across multiple sections (generation rules, best practices, common mistakes, validation checklist, troubleshooting). However, most content is genuinely necessary given the complexity of the Excalidraw JSON format. Some trimming is possible but the bulk is earned. | 2 / 3 |
Actionability | Excellent actionability with concrete, executable JSON examples for text containers, arrow bindings, and arrow labels. Specific hex color codes, pixel spacing values, font family numbers, and exact property names are provided. The code snippets are copy-paste ready and directly usable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced (UNDERSTAND → CHOOSE TYPE → EXTRACT → GENERATE → SAVE) with explicit validation via a comprehensive checklist before delivery. The checklist serves as a feedback loop to catch common errors, and the troubleshooting table provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to external files: `references/excalidraw-schema.md` for the full schema, `references/element-types.md` for extraction guidelines, `references/icon-libraries.md` for icons, and `assets/` templates for each diagram type. All references are one level deep and clearly signaled with context for when to read them. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
81e7e0d
Table of Contents
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.