drawio-skill
Skill67 starsChanged 15 days agoMITView on GitHub
Create and edit draw.io/diagrams.net diagrams as editable `.drawio` files. Covers architecture, UML/ERD/sequence, BPMN, network, and swimlane views authored from a description or converted from code, IaC, SQL, and API schemas, plus sync, query, test, review, export, and publish of existing diagrams. Use when the user asks for draw.io/diagrams.net or an editable diagram; prefer Mermaid/PlantUML when diagrams-as-code is enough.
17 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- jgeofil/agent-skillsedited, first seen Nov 8, 2026
- cadecode/agent-skillsedited, first seen Nov 1, 2026
- DaeSeokSong/oh-my-ouroborosedited, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillsedited, first seen Nov 1, 2026
- betterlmy/agent-skillstheir own version, first seen Oct 15, 2026
- zhouycheng/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use find-skills.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillfind-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- Agents365-ai/drawio-skill★ 11k88% same
- BINGWU2003/skills★ 3100% same
- DaeSeokSong/oh-my-ouroboros★ 394% same
- Big-LAORE/Biblioth-que-de-skills★ 1100% same
- cadecode/agent-skills★ 181% same
- jgeofil/agent-skills★ 0100% same
Wrote their own version · 11
- ninehills/skills★ 280same name
- jorgeasaurus/agent-skills★ 14same name
- HK-hub/AgentSkills★ 6same name
- tuoxie2046/claude-code-research-skills★ 5same name
- betterlmy/agent-skills★ 3same name
- airclear/skills★ 2same name
- bushuhui/skills★ 2same name
- xtiqny/SKILLS★ 2same name
- manastalukdar/ai-devstudio★ 1same name
- zhouycheng/skills★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analytics/AGENTS.mdAGENTS.md
- backend/AGENTS.mdAGENTS.md
- frontend/AGENTS.mdAGENTS.md
- agent-browserSkill
- archify-reviewSkill
- archifySkill
- commitSkill
- frontend-designSkill
- qualitySkill
- upgrade-backend-depsSkill
- upgrade-frontend-depsSkill
- write-prdSkill
- agent-browserSkill
- archify-reviewSkill
- archifySkill
- commitSkill
- drawio-skillSkill
- frontend-designSkill
- qualitySkill
- upgrade-backend-depsSkill
- upgrade-frontend-depsSkill
- write-prdSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 7 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
Run from this skill directory, or replace scripts/ with the absolute path to this skill's scripts directory:
- Very specific: line 85
When semantic metadata or an architecture policy is in scope, also run diagramctl.py test.
- Very specific: line 91
When the drawio binary is unavailable or a visual check is inconclusive, verify the renderer's own DOM instead (--dump-dom on the viewer …
- Distinctive: line 99
After approval, create final requested formats and report both editable source and export paths.
- Very specific: line 120
Do not combine --width and -s.
- Very specific: line 123
If the CLI crashes in a macOS sandbox, try one permitted escalated run, then use encode_drawio_url.py or deliver XML.
- Very specific: line 128
Use stable semantic IDs and never reuse reserved IDs 0 or 1.
- Very specific: line 129
Every edge requires <mxGeometry relative="1" as="geometry"/>.
- Very specific: line 132
Keep provenance, data-model-id, semantic properties, manual geometry, and manual styles intact unless the user requests otherwise.
- Distinctive: line 134
When reconciling, retain removals as reviewable faded elements by default.
- Very specific: line 155
Multi-Page Separation: When the scope spans multiple major views (e.g., deployment, data paths, execution, authentication), use a separate …
- Distinctive: line 163
Optimized Spacing: Start with edge-to-edge gaps of 150–200 px between sequential stages and 100–120 px between parallel nodes.
- Distinctive: line 166
Container Padding: Start with 40–60 px between container borders and child nodes, reserving extra space for titles and connector routes.
- Very specific: line 168
Node Sizing: Use consistent dimensions for comparable service boxes (e.g., 160 × 90 px), expanding for labels.
- Very specific: line 174
Cloud Services: When the user names a cloud provider (e.g., "in AWS"), prefer suitable services and matching available icons …
- Distinctive: line 177
Consistent Visual Language: Use the user's preferred page or example as the visual reference for all views.
- Distinctive: line 181
Icons in Flow Views: Prefer labeled icon-and-text service cards connected by concise, optionally numbered actions.
- Distinctive: line 184
Keep application roles distinct from their hosting services, and preserve sequence/state notation when needed.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Draw.io Architecture Studio
Produce editable .drawio artifacts, not flattened pictures. The preferred
entrypoint is scripts/diagramctl.py, which unifies generation, incremental
sync, multi-view projection, semantic queries/tests/reviews, failure analysis,
and accessible publishing over a shared Diagram IR.
Choose the workflow
| Request | Route |
| Natural-language diagram with precise styling | Read references/diagram-types.md, then references/xml-authoring.md and author XML |
| Standard flowchart/mindmap/gantt/timeline/etc. with no special styling | If draw.io >=30, read references/mermaid-authoring.md and convert Mermaid to native .drawio |
| Large graph (~15+ nodes) that needs automatic layout | Use autolayout.py; read references/autolayout.md before passing any --layout value |
| Code, Terraform, K8s, compose, SQL, OpenAPI, AsyncAPI, or CI source | Use diagramctl.py build; read references/diagram-ir.md |
| Protocol Buffers schema (.proto) | Use protoimports.py or diagramctl.py build; read references/toolbox.md |
| GraphQL SDL schema (.graphql/.gql) or introspection JSON | Use graphqlerd.py or diagramctl.py build; read references/toolbox.md |
| Running cluster/stack/cloud (actual state, not declared config) | Read references/live-infra.md, then use tfstate.py, dockerimports.py, or k8simports.py - |
| Update a generated diagram without losing manual layout | Use diagramctl.py sync; read references/diagram-ir.md |
| Executive/system/deployment/data-flow/security views | Use diagramctl.py views; read references/diagram-ir.md |
| Query, architecture policy, review, what-if, or guided walkthrough | Read references/semantic-workflows.md |
| MCP host (Claude Desktop, Cursor, VS Code, Codex) should call these workflows | Register scripts/diagramctl_mcp.py; read references/mcp.md |
| Prompt phrasing for a diagram type or semantic workflow | Read references/cookbook.md |
| Enforce architecture rules or visual diffs in GitHub Actions CI | Read references/ci-gate.md |
| Rendered before/after/diff images as a PR review comment | Use prdiff.py; read references/pr-bot.md |
Existing .drawio to HTML/PPTX/Mermaid/Markdown/animation/runbook | Read references/toolbox.md; diagramctl.py transform exposes the existing tools |
| Pipeline, journey, or subsystem map drawn as a metro/subway map | Use tubemap.py; read references/tubemap.md |
| Shape, cloud/vendor, AI, or Databricks icon | Read references/shapes.md or references/databricks.md; never guess shape names |
| Learn/apply/manage a visual style | Read references/style-presets.md |
| Extract a reusable style from an existing diagram or theme | Read references/style-extraction.md |
| Existing image to editable diagram (screenshot, whiteboard photo, legacy PNG) | Read references/derasterize.md |
| Export/platform problem | Read references/troubleshooting.md; for access/network questions read references/security.md |
Unified CLI
Run from this skill directory, or replace scripts/ with the absolute path to
this skill's scripts directory:
python3 scripts/diagramctl.py doctor
python3 scripts/diagramctl.py build model.json --from ir -o architecture.drawio
python3 scripts/diagramctl.py build ./infra --from terraform --group \
--ir-output architecture.ir.json -o architecture.drawio
python3 scripts/diagramctl.py sync architecture.drawio ./infra --from terraform \
-o architecture.next.drawio
python3 scripts/diagramctl.py views architecture.ir.json \
--views executive,system,deployment,dataflow,security -o views.drawio
python3 scripts/diagramctl.py test architecture.drawio --rules policy.yml
python3 scripts/diagramctl.py review architecture.drawio -o review.md
python3 scripts/diagramctl.py query architecture.drawio --from internet --to orders-db
python3 scripts/diagramctl.py whatif architecture.ir.json --fail kafka \
--drawio kafka-failure.drawio -o impact.json
python3 scripts/diagramctl.py story architecture.ir.json -o walkthrough.htmldoctor does not launch GUI tools unless --probe is passed. Core semantic
commands are offline and stdlib-only.
Creation workflow
- Infer the diagram type, audience, scope, output format, and location from the
request. Ask only when a missing choice materially changes the result;
default to PNG plus
.drawioin the working directory. - Select the authoring route from the table above. For a data-backed diagram,
prefer Diagram IR and preserve provenance. For a large graph, use an importer
or
autolayout.py; do not hand-place more than roughly fifteen nodes. - Resolve an explicitly named style preset, or the user's default preset, as
documented in
references/style-presets.md. Structural diagram conventions and visual presets compose; they do not replace each other. Generate the
.drawio, then run structural validation:python3 scripts/validate.py diagram.drawio --scoreWhen semantic metadata or an architecture policy is in scope, also run
diagramctl.py test. Do not present inferred semantic findings as verified runtime facts.- Export a draft PNG without embedded XML and inspect it visually. Fix obvious
overlap, clipping, disconnected edges, edge-through-node routing, stacked
edges, and unreadable labels. Stop automatic vision repair after two rounds.
When the drawio binary is unavailable or a visual check is inconclusive,
verify the renderer's own DOM instead (
--dump-domon the viewer URL, seereferences/troubleshooting.md): read each edge's<path>segments and label anchor coordinates directly — vision alone both misses geometry defects and hallucinates new ones. - Show the draft and apply targeted edits. Preserve existing geometry for
local changes. Use
syncfor source-backed changes and write a reviewable output; use--pruneonly when deletion was requested. - After approval, create final requested formats and report both editable source and export paths.
Export invariants
Resolve the available binary once (drawio, draw.io, the macOS app path, or
the Windows executable) and use that exact binary for the run.
# Draft for visual inspection: never use -e here
drawio -x -f png --width 2000 -o diagram.png diagram.drawio
# Final editable PNG
drawio -x -f png -e -s 2 -o diagram.drawio.png diagram.drawio
python3 scripts/repair_png.py diagram.drawio.png
# Final editable SVG/PDF
drawio -x -f svg -e --embed-svg-images -o diagram.svg diagram.drawio
drawio -x -f pdf -e -o diagram.pdf diagram.drawioDo not combine --width and -s. Embedded PNG exports require
repair_png.py; draft PNGs used by vision must not use -e. On Linux headless,
follow references/troubleshooting.md rather than improvising Electron flags.
If the CLI crashes in a macOS sandbox, try one permitted escalated run, then use
encode_drawio_url.py or deliver XML; do not repeatedly launch it.
Editing and identity
- Use stable semantic IDs and never reuse reserved IDs
0or1. - Every edge requires
<mxGeometry relative="1" as="geometry"/>. - For a local edit, change the matching cell only; for a global direction change, regenerate/re-layout the page.
- Keep provenance,
data-model-id, semantic properties, manual geometry, and manual styles intact unless the user requests otherwise. - When reconciling, retain removals as reviewable faded elements by default.
- For edges stacked at a boundary, run
edgeports.py; add waypoints when an edge still crosses an unrelated shape. There is no CLI-only edge rerouter that preserves node positions.
Quality and trust
An attractive diagram can still be wrong. Prefer source-backed relationships, show provenance where useful, distinguish exact extraction from AI inference, and keep architecture review findings framed as prompts. Story HTML must remain self-contained, keyboard usable, and include a text alternative. Never include secrets in node properties or provenance because they are embedded in outputs.
For all focused scripts and composition patterns, read references/toolbox.md;
load only the task-specific reference needed for the current request.
Architectural Views & Spatial Constraints
Apply these defaults to new architecture views; honor the requested scope, diagram conventions, and style preset. Preserve existing geometry for local edits.
- Multi-Page Separation: When the scope spans multiple major views (e.g.,
deployment, data paths, execution, authentication), use a separate page/tab for
each. Keep a focused diagram on one page; use
diagramctl.py viewsfor IR-backed multi-view output. - Self-Contained Pages: Include enough context and labeled relationships to
understand each page independently. Use orthogonal connectors
(
edgeStyle=orthogonalEdgeStyle;rounded=1;) where diagram conventions allow; use arrowheads only when the relationship is directional. - Optimized Spacing: Start with edge-to-edge gaps of 150–200 px between sequential stages and 100–120 px between parallel nodes. Adjust for labels, routing, and compactness; avoid overlaps and excessive empty space.
- Container Padding: Start with 40–60 px between container borders and child nodes, reserving extra space for titles and connector routes.
- Node Sizing: Use consistent dimensions for comparable service boxes (e.g.,
160 × 90 px), expanding for labels. Preserve vendor icon dimensions and aspect
ratios from
references/shapes.md. - Coordinate Planning: Plan grouping and routing before generation. For small, hand-authored views, calculate coordinates explicitly; for larger graphs, use the importer or automatic-layout workflow above, then inspect the result.
- Cloud Services: When the user names a cloud provider (e.g., "in AWS"),
prefer suitable services and matching available icons (
references/shapes.md) across all relevant pages; preserve source-backed facts and label proposals. - Consistent Visual Language: Use the user's preferred page or example as the visual reference for all views. Reuse component names, icons, colors, and card styling across deployment, data, execution, streaming, and authentication pages; adapt layout to each view without repeating the entire deployment topology.
- Icons in Flow Views: Prefer labeled icon-and-text service cards connected by concise, optionally numbered actions. Reuse each service's icon wherever it appears; use accurate generic symbols when no matching vendor icon exists. Keep application roles distinct from their hosting services, and preserve sequence/state notation when needed. Inspect every page for this consistency.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

