azure-resource-visualizer
Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.
59
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugin/skills/azure-resource-visualizer/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates its purpose, lists concrete actions, and provides extensive trigger terms. It follows the recommended pattern with an explicit WHEN clause containing natural user phrases. The description is concise yet comprehensive, and the Azure + Mermaid niche makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Analyze Azure resource groups', 'generate detailed Mermaid architecture diagrams', 'showing the relationships between individual resources'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyze Azure resource groups and generate Mermaid architecture diagrams showing resource relationships) and 'when' (explicit WHEN clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create architecture diagram', 'visualize Azure resources', 'show resource relationships', 'generate Mermaid diagram', 'diagram my resources', 'map Azure infrastructure', 'resource topology'. These cover many natural phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Azure resource groups + Mermaid diagrams + architecture visualization. The combination of Azure-specific terminology and Mermaid output format makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a clear logical structure and covers the Azure visualization workflow comprehensively, but suffers significantly from verbosity—explaining concepts Claude already knows (markdown formatting, Mermaid basics, general best practices) and repeating requirements across multiple sections. Actionability is moderate: it describes what to do but lacks executable, copy-paste-ready examples inline. Referenced bundle files are missing, undermining progressive disclosure.
Suggestions
Cut at least 50% of content by removing explanations of things Claude already knows (markdown heading levels, what bullet lists are for, basic Mermaid syntax) and eliminating redundancy between the workflow, guidelines, and success criteria sections.
Add a concrete, complete inline example showing a small resource group analysis producing a finished Mermaid diagram, rather than just describing the format abstractly.
Integrate a validation feedback loop into Step 3/4: e.g., render or lint the Mermaid syntax before writing the final file, with explicit fix-and-retry instructions.
Either provide the referenced bundle files (azure-resource-graph.md, example-diagram.md, template-architecture.md) or move the detailed syntax/format specifications into those files to reduce SKILL.md size.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~150+ lines. Extensively explains things Claude already knows: how to use subgraphs, markdown heading levels, bullet list formatting, what H1/H2/H3 are for. The 'Always Do / Never Do' lists repeat obvious instructions. Success criteria restates the workflow. Much of this could be cut by 60%+ without losing actionable content. | 1 / 3 |
Actionability | Provides some concrete guidance like specific az CLI commands and Mermaid syntax patterns, but most instructions are descriptive rather than executable. No complete, copy-paste-ready code examples or scripts. The MCP tool usage patterns use vague intent strings rather than actual API calls. The diagram construction section describes what to do but doesn't provide a concrete, executable template inline. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced and includes a user confirmation checkpoint at Step 1. However, there are no validation checkpoints for the critical diagram generation step (e.g., no Mermaid syntax validation step, just 'test syntax mentally'). Error handling is listed but not integrated into the workflow as feedback loops. Missing explicit verify-and-fix cycles for diagram accuracy. | 2 / 3 |
Progressive Disclosure | References to external files like 'references/azure-resource-graph.md', 'assets/example-diagram.md', and 'assets/template-architecture.md' are well-signaled and one level deep, which is good structure. However, no bundle files were provided, so these references are broken. Additionally, the main SKILL.md contains extensive inline content (Mermaid syntax specs, markdown structure specs, output format details) that should be in reference files, making the body bloated. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/github-copilot-for-azure
- Commit
dd731da
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.