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.

Quality

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable workflow that uses progressive disclosure cleanly via real one-level-deep references. Its main weakness is conciseness: several sections restate the same guidance, inflating the token budget without adding capability.

Suggestions

Consolidate 'Core Responsibilities', 'Success Criteria', and the 'Always Do' list into a single canonical checklist to remove triple restatement of the same points.

Fold the 'Output Format Specifications' Mermaid/Markdown syntax into Step 3 (Diagram Construction) and Step 4 (File Creation) instead of repeating it in a standalone section.

Trim or merge the 'Never Do' list with the relevant Edge Cases so prohibitions appear once near where they apply.

Dimension	Reasoning	Score
Conciseness	Content is actionable without explaining basic concepts Claude knows, but is padded by redundancy — 'Core Responsibilities', 'Success Criteria', and the 'Always Do' list restate one another, and 'Output Format Specifications' repeats the Mermaid syntax already given in Step 3 — so it could be tightened rather than earning the lean anchor at 3.	2 / 3
Actionability	Concrete executable `az` commands ('az resource list --resource-group <name> --output json', 'az network vnet show ...'), specific MCP intent parameters, and exact Mermaid syntax/node-ID conventions give copy-paste-ready guidance, matching the fully-executable anchor; absence of a code block is fine for this instruction-only skill.	3 / 3
Workflow Clarity	A clear four-step sequence (selection → discovery → diagram → file creation) with explicit checkpoints ('Wait for user response before proceeding', 'validate it exists') plus an Edge Cases section and checklists; the task is read-only analysis, so the destructive/batch feedback-loop cap at 2 does not apply.	3 / 3
Progressive Disclosure	The body is an overview that signals three real, one-level-deep bundle files (references/azure-resource-graph.md, assets/example-diagram.md, assets/template-architecture.md), all of which exist on disk and contain no nested references, matching the clear-overview-with-well-signaled-references anchor.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is specific, trigger-rich, and complete, naming concrete actions and an explicit WHEN clause with natural user phrasing. It occupies a clearly distinct niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources' — matching the comprehensive multi-action anchor rather than the partial domain-only anchor at 2.	3 / 3
Completeness	Explicitly answers what (analyze resource groups and generate Mermaid diagrams of relationships) and when (an explicit 'WHEN:' clause with concrete triggers), satisfying the both-answered anchor rather than the implied-when anchor at 2.	3 / 3
Trigger Term Quality	Broad natural-language triggers a user would say ('diagram my resources', 'visualize Azure resources', 'architecture visualization', 'resource topology', 'map Azure infrastructure'); coverage is strong and varied, above the partial-coverage anchor at 2.	3 / 3
Distinctiveness Conflict Risk	A clear Azure-resource + Mermaid-diagram niche with distinct triggers unlikely to fire for unrelated skills, matching the distinct-niche anchor; voice is imperative third-person ('Analyze', 'generate') with no first/second-person penalty.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/azure-skills
Commit: 39464cb

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.