devskill 2.0.7 → 2.0.8

package/skills/azure-resource-health-diagnose/SKILL.md

@@ -0,0 +1,290 @@
+---
+name: azure-resource-health-diagnose
+description: 'Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.'
+---
+
+# Azure Resource Health & Issue Diagnosis
+
+This workflow analyzes a specific Azure resource to assess its health status, diagnose potential issues using logs and telemetry data, and develop a comprehensive remediation plan for any problems discovered.
+
+## Prerequisites
+- Azure MCP server configured and authenticated
+- Target Azure resource identified (name and optionally resource group/subscription)
+- Resource must be deployed and running to generate logs/telemetry
+- Prefer Azure MCP tools (`azmcp-*`) over direct Azure CLI when available
+
+## Workflow Steps
+
+### Step 1: Get Azure Best Practices
+**Action**: Retrieve diagnostic and troubleshooting best practices
+**Tools**: Azure MCP best practices tool
+**Process**:
+1. **Load Best Practices**:
+   - Execute Azure best practices tool to get diagnostic guidelines
+   - Focus on health monitoring, log analysis, and issue resolution patterns
+   - Use these practices to inform diagnostic approach and remediation recommendations
+
+### Step 2: Resource Discovery & Identification
+**Action**: Locate and identify the target Azure resource
+**Tools**: Azure MCP tools + Azure CLI fallback
+**Process**:
+1. **Resource Lookup**:
+   - If only resource name provided: Search across subscriptions using `azmcp-subscription-list`
+   - Use `az resource list --name <resource-name>` to find matching resources
+   - If multiple matches found, prompt user to specify subscription/resource group
+   - Gather detailed resource information:
+     - Resource type and current status
+     - Location, tags, and configuration
+     - Associated services and dependencies
+
+2. **Resource Type Detection**:
+   - Identify resource type to determine appropriate diagnostic approach:
+     - **Web Apps/Function Apps**: Application logs, performance metrics, dependency tracking
+     - **Virtual Machines**: System logs, performance counters, boot diagnostics
+     - **Cosmos DB**: Request metrics, throttling, partition statistics
+     - **Storage Accounts**: Access logs, performance metrics, availability
+     - **SQL Database**: Query performance, connection logs, resource utilization
+     - **Application Insights**: Application telemetry, exceptions, dependencies
+     - **Key Vault**: Access logs, certificate status, secret usage
+     - **Service Bus**: Message metrics, dead letter queues, throughput
+
+### Step 3: Health Status Assessment
+**Action**: Evaluate current resource health and availability
+**Tools**: Azure MCP monitoring tools + Azure CLI
+**Process**:
+1. **Basic Health Check**:
+   - Check resource provisioning state and operational status
+   - Verify service availability and responsiveness
+   - Review recent deployment or configuration changes
+   - Assess current resource utilization (CPU, memory, storage, etc.)
+
+2. **Service-Specific Health Indicators**:
+   - **Web Apps**: HTTP response codes, response times, uptime
+   - **Databases**: Connection success rate, query performance, deadlocks
+   - **Storage**: Availability percentage, request success rate, latency
+   - **VMs**: Boot diagnostics, guest OS metrics, network connectivity
+   - **Functions**: Execution success rate, duration, error frequency
+
+### Step 4: Log & Telemetry Analysis
+**Action**: Analyze logs and telemetry to identify issues and patterns
+**Tools**: Azure MCP monitoring tools for Log Analytics queries
+**Process**:
+1. **Find Monitoring Sources**:
+   - Use `azmcp-monitor-workspace-list` to identify Log Analytics workspaces
+   - Locate Application Insights instances associated with the resource
+   - Identify relevant log tables using `azmcp-monitor-table-list`
+
+2. **Execute Diagnostic Queries**:
+   Use `azmcp-monitor-log-query` with targeted KQL queries based on resource type:
+
+   **General Error Analysis**:
+   ```kql
+   // Recent errors and exceptions
+   union isfuzzy=true 
+       AzureDiagnostics,
+       AppServiceHTTPLogs,
+       AppServiceAppLogs,
+       AzureActivity
+   | where TimeGenerated > ago(24h)
+   | where Level == "Error" or ResultType != "Success"
+   | summarize ErrorCount=count() by Resource, ResultType, bin(TimeGenerated, 1h)
+   | order by TimeGenerated desc
+   ```
+
+   **Performance Analysis**:
+   ```kql
+   // Performance degradation patterns
+   Perf
+   | where TimeGenerated > ago(7d)
+   | where ObjectName == "Processor" and CounterName == "% Processor Time"
+   | summarize avg(CounterValue) by Computer, bin(TimeGenerated, 1h)
+   | where avg_CounterValue > 80
+   ```
+
+   **Application-Specific Queries**:
+   ```kql
+   // Application Insights - Failed requests
+   requests
+   | where timestamp > ago(24h)
+   | where success == false
+   | summarize FailureCount=count() by resultCode, bin(timestamp, 1h)
+   | order by timestamp desc
+   
+   // Database - Connection failures
+   AzureDiagnostics
+   | where ResourceProvider == "MICROSOFT.SQL"
+   | where Category == "SQLSecurityAuditEvents"
+   | where action_name_s == "CONNECTION_FAILED"
+   | summarize ConnectionFailures=count() by bin(TimeGenerated, 1h)
+   ```
+
+3. **Pattern Recognition**:
+   - Identify recurring error patterns or anomalies
+   - Correlate errors with deployment times or configuration changes
+   - Analyze performance trends and degradation patterns
+   - Look for dependency failures or external service issues
+
+### Step 5: Issue Classification & Root Cause Analysis
+**Action**: Categorize identified issues and determine root causes
+**Process**:
+1. **Issue Classification**:
+   - **Critical**: Service unavailable, data loss, security breaches
+   - **High**: Performance degradation, intermittent failures, high error rates
+   - **Medium**: Warnings, suboptimal configuration, minor performance issues
+   - **Low**: Informational alerts, optimization opportunities
+
+2. **Root Cause Analysis**:
+   - **Configuration Issues**: Incorrect settings, missing dependencies
+   - **Resource Constraints**: CPU/memory/disk limitations, throttling
+   - **Network Issues**: Connectivity problems, DNS resolution, firewall rules
+   - **Application Issues**: Code bugs, memory leaks, inefficient queries
+   - **External Dependencies**: Third-party service failures, API limits
+   - **Security Issues**: Authentication failures, certificate expiration
+
+3. **Impact Assessment**:
+   - Determine business impact and affected users/systems
+   - Evaluate data integrity and security implications
+   - Assess recovery time objectives and priorities
+
+### Step 6: Generate Remediation Plan
+**Action**: Create a comprehensive plan to address identified issues
+**Process**:
+1. **Immediate Actions** (Critical issues):
+   - Emergency fixes to restore service availability
+   - Temporary workarounds to mitigate impact
+   - Escalation procedures for complex issues
+
+2. **Short-term Fixes** (High/Medium issues):
+   - Configuration adjustments and resource scaling
+   - Application updates and patches
+   - Monitoring and alerting improvements
+
+3. **Long-term Improvements** (All issues):
+   - Architectural changes for better resilience
+   - Preventive measures and monitoring enhancements
+   - Documentation and process improvements
+
+4. **Implementation Steps**:
+   - Prioritized action items with specific Azure CLI commands
+   - Testing and validation procedures
+   - Rollback plans for each change
+   - Monitoring to verify issue resolution
+
+### Step 7: User Confirmation & Report Generation
+**Action**: Present findings and get approval for remediation actions
+**Process**:
+1. **Display Health Assessment Summary**:
+   ```
+   🏥 Azure Resource Health Assessment
+   
+   📊 Resource Overview:
+   • Resource: [Name] ([Type])
+   • Status: [Healthy/Warning/Critical]
+   • Location: [Region]
+   • Last Analyzed: [Timestamp]
+   
+   🚨 Issues Identified:
+   • Critical: X issues requiring immediate attention
+   • High: Y issues affecting performance/reliability  
+   • Medium: Z issues for optimization
+   • Low: N informational items
+   
+   🔍 Top Issues:
+   1. [Issue Type]: [Description] - Impact: [High/Medium/Low]
+   2. [Issue Type]: [Description] - Impact: [High/Medium/Low]
+   3. [Issue Type]: [Description] - Impact: [High/Medium/Low]
+   
+   🛠️ Remediation Plan:
+   • Immediate Actions: X items
+   • Short-term Fixes: Y items  
+   • Long-term Improvements: Z items
+   • Estimated Resolution Time: [Timeline]
+   
+   ❓ Proceed with detailed remediation plan? (y/n)
+   ```
+
+2. **Generate Detailed Report**:
+   ```markdown
+   # Azure Resource Health Report: [Resource Name]
+   
+   **Generated**: [Timestamp]  
+   **Resource**: [Full Resource ID]  
+   **Overall Health**: [Status with color indicator]
+   
+   ## 🔍 Executive Summary
+   [Brief overview of health status and key findings]
+   
+   ## 📊 Health Metrics
+   - **Availability**: X% over last 24h
+   - **Performance**: [Average response time/throughput]
+   - **Error Rate**: X% over last 24h
+   - **Resource Utilization**: [CPU/Memory/Storage percentages]
+   
+   ## 🚨 Issues Identified
+   
+   ### Critical Issues
+   - **[Issue 1]**: [Description]
+     - **Root Cause**: [Analysis]
+     - **Impact**: [Business impact]
+     - **Immediate Action**: [Required steps]
+   
+   ### High Priority Issues  
+   - **[Issue 2]**: [Description]
+     - **Root Cause**: [Analysis]
+     - **Impact**: [Performance/reliability impact]
+     - **Recommended Fix**: [Solution steps]
+   
+   ## 🛠️ Remediation Plan
+   
+   ### Phase 1: Immediate Actions (0-2 hours)
+   ```bash
+   # Critical fixes to restore service
+   [Azure CLI commands with explanations]
+   ```
+   
+   ### Phase 2: Short-term Fixes (2-24 hours)
+   ```bash
+   # Performance and reliability improvements
+   [Azure CLI commands with explanations]
+   ```
+   
+   ### Phase 3: Long-term Improvements (1-4 weeks)
+   ```bash
+   # Architectural and preventive measures
+   [Azure CLI commands and configuration changes]
+   ```
+   
+   ## 📈 Monitoring Recommendations
+   - **Alerts to Configure**: [List of recommended alerts]
+   - **Dashboards to Create**: [Monitoring dashboard suggestions]
+   - **Regular Health Checks**: [Recommended frequency and scope]
+   
+   ## ✅ Validation Steps
+   - [ ] Verify issue resolution through logs
+   - [ ] Confirm performance improvements
+   - [ ] Test application functionality
+   - [ ] Update monitoring and alerting
+   - [ ] Document lessons learned
+   
+   ## 📝 Prevention Measures
+   - [Recommendations to prevent similar issues]
+   - [Process improvements]
+   - [Monitoring enhancements]
+   ```
+
+## Error Handling
+- **Resource Not Found**: Provide guidance on resource name/location specification
+- **Authentication Issues**: Guide user through Azure authentication setup
+- **Insufficient Permissions**: List required RBAC roles for resource access
+- **No Logs Available**: Suggest enabling diagnostic settings and waiting for data
+- **Query Timeouts**: Break down analysis into smaller time windows
+- **Service-Specific Issues**: Provide generic health assessment with limitations noted
+
+## Success Criteria
+- ✅ Resource health status accurately assessed
+- ✅ All significant issues identified and categorized
+- ✅ Root cause analysis completed for major problems
+- ✅ Actionable remediation plan with specific steps provided
+- ✅ Monitoring and prevention recommendations included
+- ✅ Clear prioritization of issues by business impact
+- ✅ Implementation steps include validation and rollback procedures

package/skills/azure-resource-health-diagnose/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/azure-resource-health-diagnose`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/azure-resource-visualizer/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/azure-resource-visualizer/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright 2025 (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE

package/skills/azure-resource-visualizer/SKILL.md

@@ -0,0 +1,233 @@
+---
+name: azure-resource-visualizer
+description: Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. Use this skill when the user asks for a diagram of their Azure resources or help in understanding how the resources relate to each other.
+license: Complete terms in LICENSE.txt
+metadata:
+  author: Tom Meschter (tom.meschter@microsoft.com)
+---
+
+# Azure Resource Visualizer - Architecture Diagram Generator
+
+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.
+
+## Core Responsibilities
+
+1. **Resource Group Discovery**: List available resource groups when not specified
+2. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies
+3. **Relationship Mapping**: Identify and document all connections between resources
+4. **Diagram Generation**: Create detailed, accurate Mermaid diagrams
+5. **Documentation Creation**: Produce clear markdown files with embedded diagrams
+
+## Workflow Process
+
+### Step 1: Resource Group Selection
+
+If the user hasn't specified a resource group:
+
+1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.
+2. Present a numbered list of resource groups with their locations
+3. Ask the user to select one by number or name
+4. Wait for user response before proceeding
+
+If a resource group is specified, validate it exists and proceed.
+
+### Step 2: Resource Discovery & Analysis
+
+Once you have the resource group:
+
+1. **Query all resources** in the resource group using Azure MCP tools or `az`.
+2. **Analyze each resource** type and capture:
+   - Resource name and type
+   - SKU/tier information
+   - Location/region
+   - Key configuration properties
+   - Network settings (VNets, subnets, private endpoints)
+   - Identity and access (Managed Identity, RBAC)
+   - Dependencies and connections
+
+3. **Map relationships** by identifying:
+   - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints
+   - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends
+   - **Identity**: Managed identities connecting to resources
+   - **Configuration**: App Settings pointing to Key Vaults, connection strings
+   - **Dependencies**: Parent-child relationships, required resources
+
+### Step 3: Diagram Construction
+
+Create a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format:
+
+**Diagram Structure Guidelines:**
+
+```mermaid
+graph TB
+    %% Use subgraphs to group related resources
+    subgraph "Resource Group: [name]"
+        subgraph "Network Layer"
+            VNET[Virtual Network<br/>10.0.0.0/16]
+            SUBNET1[Subnet: web<br/>10.0.1.0/24]
+            SUBNET2[Subnet: data<br/>10.0.2.0/24]
+            NSG[Network Security Group]
+        end
+        
+        subgraph "Compute Layer"
+            APP[App Service<br/>Plan: P1v2]
+            FUNC[Function App<br/>Runtime: .NET 8]
+        end
+        
+        subgraph "Data Layer"
+            SQL[Azure SQL Database<br/>DTU: S1]
+            STORAGE[Storage Account<br/>Type: Standard LRS]
+        end
+        
+        subgraph "Security & Identity"
+            KV[Key Vault]
+            MI[Managed Identity]
+        end
+    end
+    
+    %% Define relationships with descriptive labels
+    APP -->|"HTTPS requests"| FUNC
+    FUNC -->|"SQL connection"| SQL
+    FUNC -->|"Blob/Queue access"| STORAGE
+    APP -->|"Uses identity"| MI
+    MI -->|"Access secrets"| KV
+    VNET --> SUBNET1
+    VNET --> SUBNET2
+    SUBNET1 --> APP
+    SUBNET2 --> SQL
+    NSG -->|"Rules applied to"| SUBNET1
+```
+
+**Key Diagram Requirements:**
+
+- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring
+- **Include details**: SKUs, tiers, important settings in node labels (use `<br/>` for line breaks)
+- **Label all connections**: Describe what flows between resources (data, identity, network)
+- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)
+- **Visual hierarchy**: Subgraphs for logical grouping
+- **Connection types**:
+  - `-->` for data flow or dependencies
+  - `-.->` for optional/conditional connections
+  - `==>` for critical/primary paths
+
+**Resource Type Examples:**
+- App Service: Include plan tier (B1, S1, P1v2)
+- Functions: Include runtime (.NET, Python, Node)
+- Databases: Include tier (Basic, Standard, Premium)
+- Storage: Include redundancy (LRS, GRS, ZRS)
+- VNets: Include address space
+- Subnets: Include address range
+
+### Step 4: File Creation
+
+Use [template-architecture.md](./assets/template-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:
+
+1. **Header**: Resource group name, subscription, region
+2. **Summary**: Brief overview of the architecture (2-3 paragraphs)
+3. **Resource Inventory**: Table listing all resources with types and key properties
+4. **Architecture Diagram**: The complete Mermaid diagram
+5. **Relationship Details**: Explanation of key connections and data flows
+6. **Notes**: Any important observations, potential issues, or recommendations
+
+## Operating Guidelines
+
+### Quality Standards
+
+- **Accuracy**: Verify all resource details before including in diagram
+- **Completeness**: Don't omit resources; include everything in the resource group
+- **Clarity**: Use clear, descriptive labels and logical grouping
+- **Detail Level**: Include configuration details that matter for architecture understanding
+- **Relationships**: Show ALL significant connections, not just obvious ones
+
+### Tool Usage Patterns
+
+1. **Azure MCP Search**: 
+   - Use `intent="list resource groups"` to discover resource groups
+   - Use `intent="list resources in group"` with group name to get all resources
+   - Use `intent="get resource details"` for individual resource analysis
+   - Use `command` parameter when you need specific Azure operations
+
+2. **File Creation**:
+   - Always create in workspace root or a `docs/` folder if it exists
+   - Use clear, descriptive filenames: `[rg-name]-architecture.md`
+   - Ensure Mermaid syntax is valid (test syntax mentally before output)
+
+3. **Terminal (when needed)**:
+   - Use Azure CLI for complex queries not available via MCP
+   - Example: `az resource list --resource-group <name> --output json`
+   - Example: `az network vnet show --resource-group <name> --name <vnet-name>`
+
+### Constraints & Boundaries
+
+**Always Do:**
+- ✅ List resource groups if not specified
+- ✅ Wait for user selection before proceeding
+- ✅ Analyze ALL resources in the group
+- ✅ Create detailed, accurate diagrams
+- ✅ Include configuration details in node labels
+- ✅ Group resources logically with subgraphs
+- ✅ Label all connections descriptively
+- ✅ Create a complete markdown file with diagram
+
+**Never Do:**
+- ❌ Skip resources because they seem unimportant
+- ❌ Make assumptions about resource relationships without verification
+- ❌ Create incomplete or placeholder diagrams
+- ❌ Omit configuration details that affect architecture
+- ❌ Proceed without confirming resource group selection
+- ❌ Generate invalid Mermaid syntax
+- ❌ Modify or delete Azure resources (read-only analysis)
+
+### Edge Cases & Error Handling
+
+- **No resources found**: Inform user and verify resource group name
+- **Permission issues**: Explain what's missing and suggest checking RBAC
+- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer
+- **Cross-resource-group dependencies**: Note external dependencies in diagram notes
+- **Resources without clear relationships**: Group in "Other Resources" section
+
+## Output Format Specifications
+
+### Mermaid Diagram Syntax
+- Use `graph TB` (top-to-bottom) for vertical layouts
+- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)
+- Subgraph syntax: `subgraph "Descriptive Name"`
+- Node syntax: `ID["Display Name<br/>Details"]`
+- Connection syntax: `SOURCE -->|"Label"| TARGET`
+
+### Markdown Structure
+- Use H1 for main title
+- Use H2 for major sections
+- Use H3 for subsections
+- Use tables for resource inventories
+- Use bullet lists for notes and recommendations
+- Use code blocks with `mermaid` language tag for diagrams
+
+## Example Interaction
+
+**User**: "Analyze my production resource group"
+
+**Agent**:
+1. Lists all resource groups in subscription
+2. Asks user to select: "Which resource group? 1) rg-prod-app, 2) rg-dev-app, 3) rg-shared"
+3. User selects: "1"
+4. Queries all resources in rg-prod-app
+5. Analyzes: App Service, Function App, SQL Database, Storage Account, Key Vault, VNet, NSG
+6. Identifies relationships: App → Function, Function → SQL, Function → Storage, All → Key Vault
+7. Creates detailed Mermaid diagram with subgraphs
+8. Generates `rg-prod-app-architecture.md` with complete documentation
+9. Displays: "Created architecture diagram in rg-prod-app-architecture.md. Found 7 resources with 8 key relationships."
+
+## Success Criteria
+
+A successful analysis includes:
+- ✅ Valid resource group identified
+- ✅ All resources discovered and analyzed
+- ✅ All significant relationships mapped
+- ✅ Detailed Mermaid diagram with proper grouping
+- ✅ Complete markdown file created
+- ✅ Clear, actionable documentation
+- ✅ Valid Mermaid syntax that renders correctly
+- ✅ Professional, architect-level output
+
+Your goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.

package/skills/azure-resource-visualizer/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/azure-resource-visualizer`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/azure-resource-visualizer/assets/template-architecture.md

@@ -0,0 +1,41 @@
+# Azure Architecture: [Resource Group Name]
+
+**Subscription**: [subscription-name]  
+**Region**: [primary-region]  
+**Resource Count**: [count]  
+**Generated**: [date]
+
+## Overview
+
+[2-3 paragraph summary of the architecture, its purpose, and key components]
+
+## Resource Inventory
+
+| Resource Name | Type | Tier/SKU | Location | Notes |
+|--------------|------|----------|----------|-------|
+| app-prod-001 | App Service | P1v2 | East US | Production web app |
+| func-prod-001 | Function App | Y1 | East US | Consumption plan |
+
+## Architecture Diagram
+
+```mermaid
+[full diagram here]
+```
+
+## Relationship Details
+
+### Network Architecture
+[Describe VNets, subnets, network security]
+
+### Data Flow
+[Describe how data moves between components]
+
+### Identity & Access
+[Describe managed identities, key vault access, RBAC]
+
+### Dependencies
+[Describe critical dependencies and their order]
+
+## Notes & Recommendations
+
+[Any observations, potential issues, or suggestions]

package/skills/azure-role-selector/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/azure-role-selector/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright 2025 (c) Microsoft Corporation.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE

package/skills/azure-role-selector/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: azure-role-selector
+description: When user is asking for guidance for which role to assign to an identity given desired permissions, this agent helps them understand the role that will meet the requirements with least privilege access and how to apply that role.
+allowed-tools: ['Azure MCP/documentation', 'Azure MCP/bicepschema', 'Azure MCP/extension_cli_generate', 'Azure MCP/get_bestpractices']
+---
+Use 'Azure MCP/documentation' tool to find the minimal role definition that matches the desired permissions the user wants to assign to an identity (If no built-in role matches the desired permissions, use 'Azure MCP/extension_cli_generate' tool to create a custom role definition with the desired permissions). Use 'Azure MCP/extension_cli_generate' tool to generate the CLI commands needed to assign that role to the identity and use the 'Azure MCP/bicepschema' and the 'Azure MCP/get_bestpractices' tool to provide a Bicep code snippet for adding the role assignment.

package/skills/azure-role-selector/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/azure-role-selector`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24