Generate draw.io diagrams as .drawio files, optionally export to PNG/SVG/PDF with embedded XML
80
72%
Does it follow best practices?
Impact
94%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skill-cli/SKILL.mdQuality
Discovery
67%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 effectively communicates specific capabilities around draw.io diagram generation and export formats, establishing a clear niche. However, it lacks explicit trigger guidance ('Use when...') and could benefit from additional natural language terms users might use when requesting diagrams.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks for flowcharts, architecture diagrams, or mentions draw.io'
Include common user terms like 'flowchart', 'architecture diagram', 'visual diagram', 'diagram editor' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate draw.io diagrams', 'export to PNG/SVG/PDF', and 'embedded XML'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance to indicate when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'draw.io', '.drawio files', 'PNG/SVG/PDF', and 'diagrams', but missing common variations users might say like 'flowchart', 'architecture diagram', 'visual diagram', or 'diagram tool'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with 'draw.io' and '.drawio files' as specific identifiers. Unlikely to conflict with other diagramming or document skills due to the tool-specific focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent concrete examples and clear workflow sequencing. The XML format documentation is comprehensive and executable. Main weakness is the length - the detailed style reference tables and container examples could be split into separate reference files to improve token efficiency.
Suggestions
Move the detailed XML format section (common styles, style properties table, containers/groups examples) to a separate REFERENCE.md file and link to it
Remove the platform-specific CLI paths table - Claude can discover these or use 'which drawio' as already mentioned
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., the table explaining embed XML support for formats, detailed platform-specific paths that Claude could infer). The XML format section is thorough but could be tightened. | 2 / 3 |
Actionability | Provides fully executable XML examples, complete CLI commands with all flags explained, and copy-paste ready code snippets. The examples are concrete and specific with real style properties and geometry values. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow at the top with explicit sequencing. The process includes validation through the CRITICAL section on XML well-formedness, and the workflow handles conditional branching (export vs no export) clearly. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed XML reference and style properties into separate files. The external links to draw.io docs are good, but inline content is heavy. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
7df8fc7
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.