Conciseness

Nearly all content is non-obvious, draw.io-specific knowledge that earns its tokens (broken direct Mermaid→PNG export, `#create=` URL rewrite pitfall, `cmd.exe` stripping `#` fragments, edge-parenting rules for auto-layout), presented as dense commands and tables rather than prose. It is not 5 because of minor over-explanations of things Claude already knows ("Do **not** wrap it in backticks — in bash that is command substitution", the `&`-as-command-separator aside) and because ~370 lines load unconditionally when parts are platform-specific.

Actionability

Every section gives copy-paste-ready commands with real arguments: conversion (`drawio -x -f xml -o diagram.drawio diagram.mmd`), export (`drawio -x -f png -e -b 10 -o diagram.drawio.png diagram.drawio`), layout presets and custom-layout JSON, a complete Node one-liner for URL generation and a full repair-pass script, plus a ready-to-save PowerShell CLI-finder — fully executable and covering the common cases (formats, platforms, error recovery).

Workflow Clarity

The pipeline is explicitly sequenced (Author → .drawio → Deliver → Open) with a Mermaid-vs-XML decision table, an explicit validation checkpoint ("Run this right after writing XML to a .drawio file, before any layout, export or URL step" — the repair pass), conditional fallbacks (no CLI → author as XML; open fails → "print the absolute path (or URL)"), and a troubleshooting table that closes feedback loops (GPU failure → "Retry the same command with `--disable-gpu` added").

Progressive Disclosure

Good structure with well-signaled, conditional, one-level-deep references — Mermaid syntax and XML rules are fetched only when that authoring path is used ("When authoring Mermaid, fetch and follow the shared Mermaid reference"), the full XML reference only "when a diagram needs layers, tags, metadata and placeholders", and the bundled `scripts/find-shapes.js` is correctly referenced and exists in the bundle. It falls short of 5 because the ~80 lines of WSL2/Windows CLI-location chains and `.url`-file workarounds are inlined unconditionally and would sit better in a platform reference file loaded only when needed.

Specificity

Quotes: "create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch" and "diagram export to PNG/SVG/PDF" — several concrete actions with rich object coverage. It is not 5 because the verbs (create/generate/draw/design) are near-synonyms forming effectively two action categories, and concrete deliverables like .drawio file generation or browser-URL output are never named; it is above 3 because the action list and coverage are far more comprehensive than a single generic action.

Completeness

The 'when' is fully explicit ("Always use when user asks to create... or mentions draw.io...") plus environment-specific boundary guidance ("Claude Code, Codex and Copilot CLI... use this skill there"), and a 'what' is present through the named actions (diagram creation, "diagram export to PNG/SVG/PDF"). It falls short of 5 because the skill's actual outputs and mechanisms (.drawio files, Mermaid/XML authoring, layouts, browser URLs) are not explicitly stated — the 'what' is only inferred from trigger actions — but exceeds 3 since explicit trigger guidance and the domain are both clearly present.

Trigger Term Quality

Quotes: "diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch, or mentions draw.io, drawio, drawoi, .drawio files, or diagram export to PNG/SVG/PDF" — comprehensive natural-term coverage including synonyms, the product names, a common misspelling ("drawoi"), the file extension, and output formats, exactly matching the top anchor.

Distinctiveness Conflict Risk

Clear niche anchored by distinctive triggers ("draw.io, drawio, drawoi, .drawio files") and an explicit carve-out against the nearest conflict ("where the draw.io MCP server's create_diagram tool is available, call that tool instead"). Not 5 because broad terms like "mockup, wireframe, or UI sketch" and generic "diagram" carry minor overlap risk with UI-generation and general visualization skills, matching the 'minor overlap risk with closely related skills' anchor.