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.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/plugins/azure-skills/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 an explicit and comprehensive WHEN clause with numerous natural trigger terms. The description is concise, uses third-person voice correctly, and occupies a distinct niche combining Azure resource analysis with Mermaid diagram generation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyze Azure resource groups', 'generate detailed Mermaid architecture diagrams', 'showing the relationships between individual resources'. These are clear, 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). The trigger guidance is explicit and comprehensive. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'create architecture diagram', 'visualize Azure resources', 'show resource relationships', 'generate Mermaid diagram', 'analyze resource group', 'diagram my resources', 'map Azure infrastructure', 'resource topology'. These cover many natural phrasings a user might employ. | 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
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structural organization and appropriate use of progressive disclosure with external references. However, it is significantly over-verbose, with multiple sections restating the same guidance (Core Responsibilities, Operating Guidelines, Constraints, and Success Criteria all overlap). The actionability is moderate—concrete CLI commands exist but the core diagram generation lacks inline executable examples, relying instead on external files.
Suggestions
Cut 'Core Responsibilities' and 'Success Criteria' sections entirely—they restate what the workflow and guidelines already cover, saving ~40 lines of redundant content.
Merge 'Constraints & Boundaries' into the relevant workflow steps rather than listing them separately; the 'Always Do'/'Never Do' lists duplicate existing instructions.
Include a small inline Mermaid diagram example (3-5 nodes) directly in Step 3 rather than only referencing an external file, so the skill is immediately actionable.
Add an explicit validation step after diagram generation: e.g., 'Review the generated Mermaid by checking that every discovered resource appears as a node and every identified relationship appears as an edge.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with significant redundancy. The 'Core Responsibilities' section restates what the workflow already covers. 'Operating Guidelines', 'Constraints & Boundaries', and 'Success Criteria' sections heavily overlap. Many items explain things Claude already knows (markdown structure, what H1/H2/H3 are for, basic Mermaid syntax). The 'Always Do'/'Never Do' lists repeat guidance already given in the workflow steps. | 1 / 3 |
Actionability | Provides some concrete CLI commands and tool usage patterns, but much of the guidance is abstract ('Analyze each resource', 'Map relationships'). The Mermaid diagram construction section describes what to do but doesn't include a concrete inline example of a complete diagram—it defers to an external file. Tool usage patterns give intent strings but lack complete executable examples. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced and includes a user confirmation checkpoint at Step 1. However, there are no explicit validation steps for the generated Mermaid syntax (just 'test syntax mentally'), no feedback loop for verifying resource relationship accuracy, and no checkpoint between analysis and diagram generation. For a multi-step process involving complex output generation, this lacks sufficient verification. | 2 / 3 |
Progressive Disclosure | Good use of references to external files: azure-resource-graph.md for advanced queries, example-diagram.md for a sample, and template-architecture.md for the output template. These are one level deep and clearly signaled with descriptive link text. The main file serves as an overview with appropriate pointers. | 3 / 3 |
Total | 8 / 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/azure-skills
- Commit
9d594ab
- 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.