drawio

Generate Azure architecture diagrams in Draw.io from infrastructure requirements or IaC sources.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/qprjack86/apexbase --skill drawio-qprjack86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drawio
Source: https://github.com/qprjack86/apexbase/tree/main/.github/skills/drawio
Command: npx skills add https://github.com/qprjack86/apexbase --skill drawio-qprjack86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires deno, and includes references (resource) components.

What problem does it solve?

This Skill removes the friction of creating accurate Azure architecture diagrams by giving you a structured, MCP-driven workflow for turning infrastructure ideas or IaC into polished Draw.io files.

Core Features & Use Cases

  • Azure architecture diagramming: Create dependency, runtime, and as-built diagrams using the Draw.io MCP server and 700+ Azure icons.
  • Batch and transactional workflows: Build diagrams efficiently with one-shot tool calls, grouped resources, and finish/export validation.
  • IaC to diagram support: Translate Bicep, Terraform, ARM templates, or pipeline definitions into visual architecture and deployment flows.
  • Quality guardrails: Follow layout, labeling, palette, and validation rules to produce clean, reviewable diagrams.

Quick Start

Use the drawio skill to create a well-structured Azure architecture diagram from my infrastructure details and export it as a validated .drawio file.

Frequently Asked Questions about drawio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Azure architecture diagrams from Terraform or Bicep code?

Azure architecture diagram generation uses an MCP server to process infrastructure requirements and apply layout, labeling, and validation rules, producing clean, reviewable .drawio files with canonical Azure icons.

Can I create Azure dependency maps and runtime flows in Draw.io from infrastructure requirements?

Yes, creating Azure dependency maps and runtime flows in Draw.io is supported by the MCP server, which processes infrastructure requirements into structured visual diagrams with canonical Azure icons.

Does the Azure diagramming workflow support ARM templates and deployment pipeline visuals?

Yes, ARM templates and deployment pipeline definitions are supported, allowing you to translate them into visual architecture and deployment pipeline visuals for Azure workloads using batch tool calls.

Do I need Deno installed to build Draw.io diagrams for Azure workloads?

Yes, Deno is a required dependency to execute the MCP-driven workflow that generates validation-safe .drawio files for Azure workloads and runs the batch tool calls.

What is the best way to ensure my Azure architecture diagrams follow proper layout and labeling conventions?

Using a workflow with built-in quality guardrails ensures Azure architecture diagrams follow proper layout, labeling, and palette conventions, producing clean, reviewable .drawio output with 700+ canonical Azure icons.