back
loading skill details...
Create, edit, replicate, import, and export draw.io diagrams with an offline YAML-first workflow: architecture, network topologies, flowcharts, UML/ER, org…
Draw.io Base Skill Create, edit, validate, replicate, import, and export draw.io diagrams through a YAML-first offline workflow. It is the single maintained base for sibling overlays and owns the local CLI, schemas, references, themes, palettes, examples, style presets, and export helpers. Scope Use this base skill for general draw.io work: software/system architecture; network topologies and infrastructure maps; flowcharts, swimlanes, process maps, and org charts; UML class/sequence/state/ER; Mermaid and CSV conversion; structured redraw and non-academic replication; formula-bearing technical diagrams; .drawio import, sidecar export, and local validation. For paper, thesis, IEEE, journal, manuscript, or publication-ready figure requests, route to the sibling drawio-academic-skills overlay; the base does not apply academic publication gates. Without the overlay, render the local YAML bundle but report that overlay policy was not applied. Runtime Stack Use the lightest path that satisfies the request: Offline Authoring Path (default) — the YAML spec generates the final .drawio plus the default delivered image, a 300dpi PNG via draw.io Desktop (standalone SVG fallback). Desktop-Enhanced Export — 300dpi PNG default, plus PDF/JPG or embedded .drawio.svg on explicit request. Live Refinement Backend (optional) — browser refinement provider only; the offline bundle remains canonical. Provisioned by the tracked .mcp.json (pinned @next-ai-drawio/mcp-server@0.4.13, fetched over the network by npx; see references/docs/mcp-tools.md); offline authoring never reads it. Direct XML Exception — tiny one-off or raw mxGraph handoff when exact XML control is the real requirement.
don't have the plugin yet? install it then click "run inline in claude" again.