Drawio
Always use when user asks to create, generate, draw, or design a 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.From its SKILL.md
npx -y skills add juan294/cc-rpi --skill drawioAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
9.2 KB, as published. Nobody here has run it
Draw.io Diagram Skill
Generate draw.io diagrams as native .drawio files. Optionally export to PNG, SVG, or PDF with the diagram XML embedded (so the exported file remains editable in draw.io).
How to create a diagram
- Generate draw.io XML in mxGraphModel format for the requested diagram
- Write the XML to a
.drawiofile in the current working directory using the Write tool - If the user requested an export format (png, svg, pdf), locate the draw.io CLI (see below), export with
--embed-diagram, then delete the source.drawiofile. If the CLI is not found, keep the.drawiofile and tell the user they can install the draw.io desktop app to enable export, or open the.drawiofile directly - Open the result — the exported file if exported, or the
.drawiofile otherwise. If the open command fails, print the file path so the user can open it manually
Choosing the output format
Check the user's request for a format preference. Examples:
/drawio create a flowchart→flowchart.drawio/drawio png flowchart for login→login-flow.drawio.png/drawio svg: ER diagram→er-diagram.drawio.svg/drawio pdf architecture overview→architecture-overview.drawio.pdf
If no format is mentioned, just write the .drawio file and open it in draw.io. The user can always ask to export later.
Supported export formats
| Format | Embed XML | Notes |
|---|---|---|
png | Yes (-e) | Viewable everywhere, editable in draw.io |
svg | Yes (-e) | Scalable, editable in draw.io |
pdf | Yes (-e) | Printable, editable in draw.io |
jpg | No | Lossy, no embedded XML support |
PNG, SVG, and PDF all support --embed-diagram — the exported file contains the full diagram XML, so opening it in draw.io recovers the editable diagram.
draw.io CLI
The draw.io desktop app includes a command-line interface for exporting.
Locating the CLI
First, detect the environment, then locate the CLI accordingly:
WSL2 (Windows Subsystem for Linux)
WSL2 is detected when /proc/version contains microsoft or WSL:
grep -qi microsoft /proc/version 2>/dev/null && echo "WSL2"
On WSL2, use the Windows draw.io Desktop executable via /mnt/c/...:
DRAWIO_CMD=`/mnt/c/Program Files/draw.io/draw.io.exe`
The backtick quoting is required to handle the space in Program Files in bash.
If draw.io is installed in a non-default location, check common alternatives:
# Default install path
`/mnt/c/Program Files/draw.io/draw.io.exe`
# Per-user install (if the above does not exist)
`/mnt/c/Users/$WIN_USER/AppData/Local/Programs/draw.io/draw.io.exe`
macOS
/Applications/draw.io.app/Contents/MacOS/draw.io
Linux (native)
drawio # typically on PATH via snap/apt/flatpak
Windows (native, non-WSL2)
"C:\Program Files\draw.io\draw.io.exe"
Use which drawio (or where drawio on Windows) to check if it's on PATH before falling back to the platform-specific path.
Export command
drawio -x -f <format> -e -b 10 -o <output> <input.drawio>
WSL2 example:
`/mnt/c/Program Files/draw.io/draw.io.exe` -x -f png -e -b 10 -o diagram.drawio.png diagram.drawio
Key flags:
-x/--export: export mode-f/--format: output format (png, svg, pdf, jpg)-e/--embed-diagram: embed diagram XML in the output (PNG, SVG, PDF only)-o/--output: output file path-b/--border: border width around diagram (default: 0)-t/--transparent: transparent background (PNG only)-s/--scale: scale the diagram size--width/--height: fit into specified dimensions (preserves aspect ratio)-a/--all-pages: export all pages (PDF only)-p/--page-index: select a specific page (1-based)
Opening the result
| Environment | Command |
|---|---|
| macOS | open <file> |
| Linux (native) | xdg-open <file> |
| WSL2 | cmd.exe /c start "" "$(wslpath -w <file>)" |
| Windows | start <file> |
WSL2 notes:
wslpath -w <file>converts a WSL2 path (e.g./home/user/diagram.drawio) to a Windows path (e.g.C:\Users\...). This is required becausecmd.execannot resolve/mnt/c/...style paths.- The empty string
""afterstartis required to preventstartfrom interpreting the filename as a window title.
WSL2 example:
cmd.exe /c start "" "$(wslpath -w diagram.drawio)"
File naming
- Use a descriptive filename based on the diagram content (e.g.,
login-flow,database-schema) - Use lowercase with hyphens for multi-word names
- For export, use double extensions:
name.drawio.png,name.drawio.svg,name.drawio.pdf— this signals the file contains embedded diagram XML - After a successful export, delete the intermediate
.drawiofile — the exported file contains the full diagram
XML format
A .drawio file is native mxGraphModel XML. Always generate XML directly — Mermaid and CSV formats require server-side conversion and cannot be saved as native files.
Basic structure
Every diagram must have this structure:
<mxGraphModel adaptiveColors="auto">
<root>
<mxCell id="0"/>
<mxCell id="1" parent="0"/>
<!-- Diagram cells go here with parent="1" -->
</root>
</mxGraphModel>
- Cell
id="0"is the root layer - Cell
id="1"is the default parent layer - All diagram elements use
parent="1"unless using multiple layers
XML reference
Common styles
Rounded rectangle:
<mxCell id="2" value="Label" style="rounded=1;whiteSpace=wrap;" vertex="1" parent="1">
<mxGeometry x="100" y="100" width="120" height="60" as="geometry"/>
</mxCell>
Diamond (decision):
<mxCell id="3" value="Condition?" style="rhombus;whiteSpace=wrap;" vertex="1" parent="1">
<mxGeometry x="100" y="200" width="120" height="80" as="geometry"/>
</mxCell>
Arrow (edge):
<mxCell id="4" value="" style="edgeStyle=orthogonalEdgeStyle;" edge="1" source="2" target="3" parent="1">
<mxGeometry relative="1" as="geometry"/>
</mxCell>
Style properties
| Property | Values | Use for |
|---|---|---|
rounded=1 | 0 or 1 | Rounded corners |
whiteSpace=wrap | wrap | Text wrapping |
fillColor=#dae8fc | Hex color | Background color |
strokeColor=#6c8ebf | Hex color | Border color |
fontColor=#333333 | Hex color | Text color |
shape=cylinder3 | shape name | Database cylinders |
ellipse | style keyword | Circles/ovals |
rhombus | style keyword | Diamonds |
edgeStyle=orthogonalEdgeStyle | style keyword | Right-angle connectors |
dashed=1 | 0 or 1 | Dashed lines |
swimlane | style keyword | Swimlane containers |
group | style keyword | Invisible container |
container=1 | 0 or 1 | Enable container behavior |
Edge routing
CRITICAL: Every edge mxCell must contain a <mxGeometry relative="1" as="geometry" /> child element. Self-closing edge cells are invalid.
- Use
edgeStyle=orthogonalEdgeStylefor right-angle connectors - Space nodes generously — 200px horizontal / 120px vertical gaps
- Use
exitX/exitYandentryX/entryY(0-1) to control connection points - Leave at least 20px for arrowheads
- Add explicit waypoints for overlapping edges
Containers
Set parent="containerId" on child cells. Children use relative coordinates.
| Type | Style | When to use |
|---|---|---|
| Group (invisible) | group; | No visual border needed |
| Swimlane (titled) | swimlane;startSize=30; | Needs visible title bar |
| Custom container | container=1;pointerEvents=0; | Any shape as container |
Dark mode
Use adaptiveColors="auto" on mxGraphModel. Explicit colors auto-invert. Use light-dark(lightColor,darkColor) for manual control.
CRITICAL: XML well-formedness
- NEVER include ANY XML comments (
<!-- -->) in the output. XML comments are strictly forbidden. - Escape special characters in attribute values:
&,<,>," - Always use unique
idvalues for eachmxCell