drawio skill

Data Community v1.14.0

Skill notes

Overview

Generate .drawio XML files and export to PNG/SVG/PDF/JPG locally using the native draw.io desktop app CLI. Supported formats: PNG, SVG, PDF, JPG — no browser automation needed. PNG, SVG, and PDF exports support --embed-diagram (-e) — the exported file contains the full diagram XML, so opening it in draw.io recovers the editable diagram. Use double extensions (name.drawio.png) to signal embedded XML.

When to use / when NOT to use

Use this skill for: polished, precise diagrams (architecture, network, strict UML, ERD), anything needing solid opaque fills, 10,000+ stock/branded shapes, swimlanes, or custom geometry, exported as editable PNG/SVG/PDF. Do NOT use it — route elsewhere — for: A casual hand-drawn / whiteboard look → excalidraw or tldraw. Diagrams-as-code that live in git / render in Markdown → mermaid (general) or plantuml (UML).

Bundled resources

When the workflow references one of these, read it on demand — none of them need to be in context up front. File · Read it when references/diagram-types.md · The user names a specific diagram type (ERD, UML class, sequence, architecture, ML/DL, flowchart) references/shapes.md + scripts/shapesearch.py · The diagram needs a specific shape — a cloud icon (AWS/Azure/GCP), Cisco/Kubernetes/network symbol, UML/BPMN/ER/electrical/P&ID element — or any time you'd otherwise guess a style= string. shapesearch.py "<keywords>" returns the exact official style for 10k+ shapes

Prerequisites

The draw.io desktop app must be installed and the CLI accessible: macOS sandbox / sandbox isolation note (e.g., codex.app): In some sandboxed macOS environments, invoking the draw.io desktop CLI (even drawio --version) can crash the draw.io process or produce no output. If that happens, treat the CLI as unavailable in this sandbox isolation — do not keep retrying inside the sandbox. Prefer a non-sandboxed host environment (outside sandbox isolation) for any CLI export work, or use the browser fallback / XML-only outputs.

Workflow

Before starting the workflow, assess whether the user's request is specific enough. If key details are missing, ask 1-3 focused questions: Diagram type — which preset? (ERD, UML, Sequence, Architecture, ML/DL, Flowchart, or general) Output format — PNG (default), SVG, PDF, or JPG? Output location — default is the user's working dir; honor any explicit path the user gives (e.g. "put it in ./artifacts/"). Don't ask if they didn't mention one.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
98 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Agents365-ai · v1.14.0 · MIT
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Windows · Docker
Runtime requirements
Node.js · Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 5: Self-Check

After exporting the draft PNG, use the agent's vision capability (e.g., Claude's image input) to read the image and check for these issues before showing the user. If the agent does not support vision, skip self-check and show the PNG directly.

02
Step 6: Review Loop

After self-check, show the exported image and ask the user for feedback. Targeted edit rules — for each type of feedback, apply the minimal XML change: User request · XML edit action Change color of X · Find `mxCell` by `value` matching X, update `fillColor`/`strokeColor` in `style` Add a new node · Append a new `mxCell` vertex with next available `id`, position near related nodes

03
Step 7: Final Export

Once the user approves: Export to all requested formats (PNG, SVG, PDF, JPG) — default to PNG if not specified Report file paths for both the `.drawio` source file and exported image(s) Auto-launch: offer to open the `.drawio` file in draw.io desktop for fine-tuning — `open diagram.drawio` (macOS), `xdg-open` (Linux), `start` (Windows) Confirm files are saved and ready to use

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.