drawio
Generate draw.io diagrams as .drawio files, optionally export to PNG/SVG/PDF with embedded XML
77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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, with good distinctiveness due to the tool-specific terminology. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'flowchart' or 'architecture diagram' that users commonly say when needing diagramming help.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user asks for diagrams, flowcharts, architecture visuals, or mentions draw.io'
Include common diagram type keywords users naturally say: 'flowchart', 'architecture diagram', 'sequence diagram', 'visual diagram', 'diagram tool'
| 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' (generate diagrams, export to various formats) but lacks an explicit 'Use when...' clause or trigger guidance for 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 specific niche with 'draw.io' and '.drawio files' as distinct identifiers. Unlikely to conflict with other diagramming or document skills due to the specific tool reference. | 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 well-structured, highly actionable skill with clear workflows and executable examples. The main weakness is verbosity - the extensive style reference tables, edge routing details, and container examples could be condensed or moved to separate reference files. The skill successfully teaches draw.io diagram generation but uses more tokens than necessary for some sections.
Suggestions
Move the detailed style properties table and container examples to a separate REFERENCE.md file, keeping only the most essential styles inline
Condense the edge routing section - the arrowhead spacing explanation is overly detailed for what could be a simple 'ensure 20px minimum final segment' rule
Consider removing the 'Useful style properties' table entirely and just linking to the external draw.io style reference, since Claude can look it up
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary detail like the full table of style properties and extensive edge routing explanations that could be condensed. The container section is thorough but somewhat verbose for what Claude likely already understands about XML parent-child relationships. | 2 / 3 |
Actionability | Provides fully executable XML examples, specific CLI commands with all flags explained, platform-specific paths, and copy-paste ready code snippets. The examples are concrete and complete, not pseudocode. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow at the top with explicit sequencing. The process includes validation through the 'CRITICAL: XML well-formedness' section, 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 reference material (style properties, edge routing, container examples) 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 | |
- 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.