azure-resource-visualizer_skill

Overview

This skill analyzes Azure resource groups and generates clear, detailed Mermaid architecture diagrams that show relationships between individual resources. It inspects resource metadata, network settings, identity links, and dependency chains to produce accurate visualizations and a companion markdown summary. Use it to quickly understand topology, data flows, and security boundaries in any Azure resource group.

How this skill works

The skill discovers or validates the target resource group, enumerates all resources, and collects key properties (SKU, region, network settings, identities). It maps network connections, data flows, managed identities, and configuration references, then builds a structured Mermaid diagram using subgraphs for logical layers. Finally, it produces a markdown file with the diagram, a resource inventory table, relationship explanations, and actionable notes.

When to use it

• You need a visual architecture diagram for a specific Azure resource group.
• Investigating dependencies before making configuration or deployment changes.
• Auditing network boundaries, private endpoints, or identity usage.
• Onboarding new team members to understand an environment quickly.
• Preparing documentation for architecture reviews or security assessments.

Best practices

• Specify the resource group when possible; otherwise the skill will list groups and wait for selection.
• Provide credentials or allow read-only Azure CLI access so resource details can be validated.
• For large groups (50+ resources), ask for layered diagrams (network, compute, data) to keep diagrams readable.
• Verify RBAC permissions if some resources are missing or details are incomplete.
• Review generated markdown and Mermaid output; adjust node labels to include any organization-specific names or tags.

Example use cases

• Generate a top-to-bottom Mermaid diagram showing VNets, subnets, App Services, Functions, SQL, Storage, and Key Vaults for a production RG.
• Audit private endpoint placements and NSG relationships to find unintended exposure paths.
• Document cross-resource-group dependencies and list external resources referenced by app settings or connection strings.
• Create a markdown architecture file for a sprint handoff or an operational runbook.