Generate draw.io diagrams programmatically using Python. Creates flowcharts, architecture diagrams, tree structures, network diagrams, and more. Use when the user requests a .drawio file, diagram, flowchart, or visual documentation.
89
86%
Does it follow best practices?
Impact
89%
3.17xAverage score across 3 eval scenarios
Passed
No known issues
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 a strong skill description that clearly communicates what the skill does (generates draw.io diagrams programmatically using Python across multiple diagram types), when to use it (explicit trigger clause with natural terms like .drawio, diagram, flowchart), and occupies a distinct niche. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate draw.io diagrams programmatically using Python', 'Creates flowcharts, architecture diagrams, tree structures, network diagrams'. These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate draw.io diagrams programmatically using Python, creates flowcharts/architecture diagrams/tree structures/network diagrams) and 'when' (explicit 'Use when the user requests a .drawio file, diagram, flowchart, or visual documentation'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: '.drawio file', 'diagram', 'flowchart', 'visual documentation', 'architecture diagrams', 'network diagrams'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinct niche: draw.io diagrams via Python. The mention of '.drawio file' and specific diagram types makes it unlikely to conflict with general diagramming or other visualization skills. The tool and output format are well-defined. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 skill with strong actionability and good progressive disclosure. The main weaknesses are minor verbosity (explaining things Claude already knows like what draw.io files are) and the lack of validation/verification steps after generating diagrams. The decision tree is a particularly effective pattern for routing to the right approach.
Suggestions
Remove the bullet list explaining where .drawio files can be opened — Claude already knows this.
Add a validation step after file generation, e.g., verifying the file exists and is valid XML, or opening/parsing it to confirm structure before presenting to the user.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary content — the overview explaining what draw.io files can be opened in is information Claude already knows, and the inline dependency metadata explanation could be trimmer. The decision tree and shape library lists are useful but slightly verbose. | 2 / 3 |
Actionability | Provides fully executable code examples with proper imports, concrete commands for running scripts, specific library/shape names for object_from_library, and clear parameter details. The quick start example is copy-paste ready. | 3 / 3 |
Workflow Clarity | The decision tree provides good routing for diagram type selection, and the quick start shows a clear sequence. However, there are no validation checkpoints — no guidance on verifying the output file is valid XML/drawio, no error handling steps, and no feedback loop for when diagram generation fails or produces unexpected results. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick start, key concepts inline, and clear one-level-deep references to REFERENCE.md, examples.md, and helper scripts. Content is appropriately split between the skill file and reference materials. | 3 / 3 |
Total | 10 / 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.
3f74412
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.