Add azure-resource-visualizer skill

[tmeschter]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, or chat mode file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, or chat mode with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

This change adds a skill that can analyze the resources within an Azure resource group, determine the relationships between them, and then generate a Markdown file containing the relevant details. The Markdown file includes a Mermaid diagram showing the relationships.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New chat mode file.
• New collection file.
• Update to existing instruction, prompt, chat mode, or collection.
• Other (please specify): New skill.

---

Additional Notes

Here is an example diagram showing an MCP server hosted in Azure Functions:

graph TB
    subgraph "Resource Group: rg-joke-mcp"
        subgraph "Compute Layer - East US"
            PLAN[App Service Plan<br/>ASP-rgjokemcp-67ea<br/>Tier: FlexConsumption FC1<br/>Max Instances: 100]
            FUNC[Function App<br/>func-joke-mcp-9426<br/>Runtime: .NET 8 isolated<br/>Memory: 2048 MB<br/>Public Access: Disabled]
            MI[System Assigned<br/>Managed Identity<br/>Principal ID: 85813040...]
        end
        
        subgraph "Storage Layer"
            ST1[Storage Account<br/>stjokemcp6331<br/>East US<br/>Type: Standard LRS<br/>No Public Blob Access<br/>HTTPS Only]
            ST2[Storage Account<br/>stjokemcp2522<br/>West US 2<br/>Type: Standard LRS<br/>No Public Blob Access<br/>HTTPS Only]
            BLOB1[Blob Container<br/>app-package-funcjokemcp9426-*<br/>Function deployment package]
        end
        
        subgraph "Monitoring & Observability"
            AI[Application Insights<br/>func-joke-mcp-9426<br/>Type: LogAnalytics<br/>Retention: 90 days]
            LAW[Log Analytics Workspace<br/>DefaultWorkspace-*-EUS<br/>Centralized logs]
            ALERT[Smart Detector Alert<br/>Failure Anomalies<br/>AI-powered detection]
        end
        
        subgraph "Event-Driven Infrastructure"
            EG1[Event Grid System Topic<br/>stjokemcp6331-*<br/>Storage Events]
            EG2[Event Grid System Topic<br/>stjokemcp2522-*<br/>Storage Events]
        end
    end
    
    %% Compute relationships
    FUNC -->|"Hosted on"| PLAN
    FUNC -->|"Uses identity"| MI
    
    %% Storage relationships
    MI -->|"System Assigned Identity<br/>Blob access for deployment"| ST1
    MI -->|"Potential access"| ST2
    ST1 -->|"Contains"| BLOB1
    BLOB1 -->|"Deployment source"| FUNC
    
    %% Monitoring relationships
    FUNC -->|"Sends telemetry"| AI
    AI -->|"Writes logs to"| LAW
    AI -->|"Triggers"| ALERT
    FUNC -->|"Function logs"| LAW
    
    %% Event Grid relationships
    ST1 -->|"Emits storage events"| EG1
    ST2 -->|"Emits storage events"| EG2
    EG1 -.->|"Can trigger"| FUNC
    EG2 -.->|"Can trigger"| FUNC
    
    %% External access
    USERS[External Users/Clients]
    USERS -->|"HTTPS requests<br/>*.azurewebsites.net"| FUNC

    classDef compute fill:#0078d4,stroke:#004578,color:#fff
    classDef storage fill:#50e6ff,stroke:#0078d4,color:#000
    classDef monitoring fill:#ff9900,stroke:#cc7a00,color:#000
    classDef events fill:#68217a,stroke:#4a1755,color:#fff
    classDef identity fill:#00bcf2,stroke:#008db3,color:#000
    
    class PLAN,FUNC compute
    class ST1,ST2,BLOB1 storage
    class AI,LAW,ALERT monitoring
    class EG1,EG2 events
    class MI identity

Loading

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull request overview

This PR adds a new Agent Skill called azure-resource-visualizer that analyzes Azure resource groups and generates detailed Mermaid architecture diagrams showing relationships between resources. The skill helps users understand complex Azure architectures through visualization.

Key Changes:

• Adds a comprehensive skill with detailed instructions for Azure resource analysis and diagram generation
• Includes a template file to guide output format
• Updates the skills documentation registry

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
skills/azure-resource-visualizer/SKILL.md	Main skill definition with comprehensive instructions for analyzing Azure resources, mapping relationships, and generating Mermaid diagrams
skills/azure-resource-visualizer/assets/template-architecture.md	Template file that defines the structure for the generated architecture documentation
skills/azure-resource-visualizer/LICENSE.txt	MIT License file for the skill
docs/README.skills.md	Updated skills registry table to include the new azure-resource-visualizer skill

[tmeschter]

@digitarald I'm not sure what is needed to make the "Validate README.md" check happy. I've rebased my branch onto the latest main, run npm start locally (this generated no changes), and pushed the branch.

[digitarald]

Copilot is working on a fix for:

I can see the issue! In update-readme.mjs:532-533, the script uses path.relative() which returns paths with forward slashes on Unix/macOS and the file uses path.join() in yaml-parser.mjs:165-180 which on Windows would create backslashes.
The PR was created on Windows (notice the backslash in the diff: assets\template-architecture.md), but the CI runs on Ubuntu (Linux), which normalizes paths to use forward slashes.

[digitarald]

Issue Identified and Fixed

The CI failure was caused by a cross-platform path separator issue. Your skill was created on Windows, which uses backslashes (\) for file paths, but the CI runs on Linux, which uses forward slashes (/).

What Happened

In docs/README.skills.md, the bundled assets were listed as:

assets\template-architecture.md

When the CI regenerated the README on Linux, it normalized the path to:

assets/template-architecture.md

This created a diff that caused the validation check to fail.

The Fix

I've pushed a fix to main in commit f548156 that normalizes all path separators to forward slashes (/) in the build script, regardless of the platform where the skill was created.

Next Steps for You

To resolve this PR:

1. Rebase your branch on the latest main:

   git fetch upstream
   git rebase upstream/main

2. Regenerate the README with the fixed script:

   npm start

3. Commit and push the updated README:

   git add docs/README.skills.md
   git commit -m "Update generated README with normalized path separators"
   git push --force-with-lease

The CI should pass after this! 🎉

[tmeschter]

@digitarald This is ready for a new review.

[aaronpowell]

@tmeschter can you fix the merge conflict then it probably can merge