draw-io
draw.io diagram creation, editing, and review. Use for .drawio XML editing, PNG conversion, layout adjustment, and AWS icon usage.
Overall
score
93%
Does it follow best practices?
Validation for skill structure
Discovery
85%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 defines its scope around draw.io diagrams with specific capabilities and explicit usage triggers. The main weakness is the trigger term coverage, which focuses on technical terms but may miss users who ask about 'flowcharts', 'diagrams', or 'architecture diagrams' without mentioning draw.io specifically.
Suggestions
Add common user-facing terms like 'flowchart', 'architecture diagram', 'visual diagram', or 'diagramming' to improve trigger term coverage for users who may not know the tool name.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'diagram creation, editing, and review', '.drawio XML editing, PNG conversion, layout adjustment, and AWS icon usage' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('diagram creation, editing, and review') and when ('Use for .drawio XML editing, PNG conversion, layout adjustment, and AWS icon usage') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good technical terms like 'draw.io', '.drawio', 'XML', 'PNG', 'AWS icon', but misses common user variations like 'flowchart', 'diagram', 'architecture diagram', or 'visual diagram'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with distinct triggers - 'draw.io', '.drawio XML', and 'AWS icon usage' are highly specific and unlikely to conflict with other diagramming or document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that demonstrates strong technical writing. It efficiently covers draw.io diagram creation with concrete XML examples, clear workflows, and comprehensive best practices. The checklist provides effective validation, and the progressive disclosure through external references keeps the main document focused.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting information in tables, code blocks, and bullet points without explaining concepts Claude already knows. Every section provides specific, actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable commands, complete XML examples, and specific coordinate calculations. Code snippets are copy-paste ready with clear option explanations in tables. | 3 / 3 |
Workflow Clarity | Section 4.1 provides clear sequential steps for coordinate adjustment with explicit verification step. The checklist in Section 8 serves as a comprehensive validation checkpoint, and multiple sections emphasize 'verify in PNG' as feedback loops. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section hierarchy. References to external files (layout guidelines, AWS icons, scripts) are one level deep and clearly signaled in Section 7. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 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.