$ loading_
Analyze Azure resource groups and generate Mermaid diagrams of resource relationships.
The material describes an open-source, primarily prompt-based architecture analysis/diagramming skill with no declared secrets or fixed remote endpoints, so overall risk appears low. Caution is still warranted because its workflow may use Azure MCP tools or az to inspect resource groups and configurations, which can access cloud metadata in a real environment.
No extra API keys, tokens, or environment variables are declared. The README only mentions using Azure MCP tools or az for queries, does not ask to collect or output credentials, and explicitly says not to place secret values in diagrams.
No remote endpoints are declared, and the system marks it as prompt-only; the material does not show an independent data exfiltration path. If it operates via Azure MCP tools or az in practice, any network traffic would be the ordinary Azure queries implied by its stated purpose.
The README explicitly says to use az if no tool is available, indicating that in some host environments the skill may invoke local CLI/tools to run query commands. This kind of local process execution is a normal tool capability, and no execution beyond its stated purpose or privilege escalation is evident.
Its purpose is to analyze resource groups, resource relationships, network settings, identities, and configurations, so it may read Azure resource metadata, connectivity, and config details. Although the docs require placeholders for secret values, it can still expose sensitive architecture information. There is no sign of writing sensitive local files or requesting permissions unrelated to its function.
The source is an open-source Microsoft GitHub repository with auditable code and 222 stars, both positive trust signals that lower risk. The missing license declaration and unknown maintenance status add minor uncertainty, but not enough on their own to justify a high-risk rating.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "azure-resource-visualizer" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/plugin/skills/azure-resource-visualizer/SKILL.md 2. Save it as ~/.claude/skills/azure-resource-visualizer/SKILL.md 3. Reload skills and tell me it's ready
Analyze my Azure resource group and output a Mermaid architecture diagram showing relationships among virtual networks, virtual machines, storage accounts, databases, and load balancers, grouped by resource type.
Mermaid diagram code that clearly shows grouped resources, connections, and the overall architecture topology.
Review the resource dependencies in this Azure resource group, generate a Mermaid diagram, and indicate which resources are directly connected and which are core dependency nodes.
A Mermaid relationship diagram highlighting dependency paths and key nodes to clarify impact across resources.
Turn this Azure resource group into a Mermaid architecture diagram suitable for technical documentation, with clear naming, distinct layers, and brief notes on the role of major resources.
A documentation-ready Mermaid diagram with brief explanations, suitable for team sharing and maintenance.
A user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.
If the user hasn't specified a resource group:
az.If a resource group is specified, validate it exists and proceed.
For bulk resource discovery across subscriptions, use Azure Resource Graph queries. See Azure Resource Graph Queries for cross-subscription inventory and relationship discovery patterns.
Once you have the resource group:
Query all resources in the resource group using Azure MCP tools or az.
Analyze each resource type and capture:
Map relationships by identifying:
Important: You must only use placeholder names to represent secret values, such as keys, connection strings, Key Vault secrets, etc. Use meaningful placeholder names to represent each secret in the diagram. Never put secret values in the resource diagram.
Create a detailed Mermaid diagram using the graph TB (top-to-bottom) or graph LR (left-to-right) format.
See example-diagram.md for a complete sample architecture diagram.
Key Diagram Requirements:
<br/> for line breaks)--> for data flow or dependencies-.-> for optional/conditional connections==> for critical/primary pathsResource Type Examples:
Use template-architecture.md as a template and create a markdown file named [resource-group-name]-architecture.md with:
…
Set up Entra ID app registration, OAuth, permissions, and MSAL integration.
Set up Azure Application Insights telemetry for web apps with best practices.
Troubleshoot Azure Event Hubs and Service Bus SDK connection and messaging issues.
Find, list, and inspect Azure resources across subscriptions and resource groups.
Deploy, evaluate, fine-tune, and optimize Microsoft Foundry agents and models.
Deploy prepared Azure apps with built-in recovery for common release errors.
Generate accurate multi-cloud architecture diagrams for technical design and communication.
Analyze cloud architectures and generate recommendations, diagrams, and ADRs across major clouds.
Generate consistent Azure architecture diagrams safely from topology descriptions.
Analyze codebase architecture, inspect dependencies, and generate interactive visual diagrams.
Generate enterprise architecture diagrams in Visio from prompts or inventory data.
Create polished architecture diagrams with theme switching and multi-format export.