CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured, highly actionable skill with an exemplary progressive-disclosure bundle (one reference + two assets, all real, relevant, and linked at point of use). The main weaknesses are redundancy — the same requirements are restated across four checklist-style sections — and a soft 'test syntax mentally' validation step where an explicit validate-and-fix loop would be stronger.

Suggestions

Collapse 'Core Responsibilities', 'Quality Standards', 'Always Do / Never Do', and 'Success Criteria' into a single requirements section — they restate the same guidance three to four times and account for most of the excess length.

Replace 'Ensure Mermaid syntax is valid (test syntax mentally before output)' with an explicit validation step, e.g. re-render or lint the diagram and fix/re-check on failure, to create a real feedback loop in Step 3→4.

Name the exact Azure MCP tool invocations in the Tool Usage Patterns section (as azure-resource-graph.md already does for `az graph query`) so the main body's tool guidance is copy-paste ready without loading the reference.

DimensionReasoningScore

Conciseness

The body never teaches concepts Claude already knows and each section is individually tight, but requirements are restated three-plus times across "Core Responsibilities", "Quality Standards", "Always Do / Never Do", and "Success Criteria" (e.g., 'Analyze ALL resources' appears as both a workflow step, a ✅ item, and a success criterion), so it could be cut substantially — matching 'mostly efficient but could be tightened'. Not a 2 because there is no fluff prose or unnecessary explanation, only repetition of genuinely task-specific guidance.

3 / 5

Actionability

Provides concrete commands ("az resource list --resource-group <name> --output json"), exact Mermaid syntax ("SOURCE -->|\"Label\"| TARGET", "ID[\"Display Name<br/>Details\"]"), concrete resource-detail examples ("B1, S1, P1v2", "LRS, GRS, ZRS"), and a linked template plus example diagram — mostly executable guidance. Not a 5 because the MCP tool invocations in the body are given only as intent strings ("intent=\"list resource groups\"") without the actual tool names, which live only in the reference file, leaving a minor gap.

4 / 5

Workflow Clarity

A clear four-step sequence with most checkpoints present: wait-for-user-selection and validate-group-exists before proceeding, "Verify all resource details before including in diagram", an Edge Cases & Error Handling section (empty groups, permission issues, 50+ resources), and a read-only boundary. Not a 5 because the Mermaid validation step is only "test syntax mentally before output" — there is no explicit validate-and-retry loop or concrete validation mechanism, which the top anchor expects.

4 / 5

Progressive Disclosure

The body is a workflow overview with details appropriately split one level deep and clearly signaled at point of use: "See [Azure Resource Graph Queries](references/azure-resource-graph.md)" for bulk querying, "[example-diagram.md](./assets/example-diagram.md)" for a complete sample, and "[template-architecture.md](./assets/template-architecture.md)" for output structure — all three files exist and contain the promised material. Navigation is easy and nothing bulk (API reference, examples) is inlined that should be external, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what-and-when structure and excellent natural-language trigger coverage. The only notable gap is that the action list stops at two, omitting concrete outputs like the markdown architecture-document and resource-inventory table that the skill actually produces.

Suggestions

Add the documentation deliverable to the action list, e.g. "...and produce a markdown architecture document with a resource inventory table" — this closes the specificity gap without adding fluff.

Qualify the remaining generic triggers (e.g., "create architecture diagram" → "create Azure architecture diagram") to eliminate the minor conflict risk with generic diagramming skills.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions — "Analyze Azure resource groups" and "generate detailed Mermaid architecture diagrams showing the relationships between individual resources" — which matches the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because two actions is not 'several' (e.g., it omits the documentation/inventory-file output the skill produces), and not below 3 because the actions given are genuinely concrete rather than generic.

3 / 5

Completeness

Explicitly answers both 'what' ("Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources") and 'when' via a dedicated "WHEN:" clause with concrete trigger phrases, matching the top anchor exactly. Not a 4 because the when-guidance is not merely present but explicit, specific, and multi-phrase.

5 / 5

Trigger Term Quality

The WHEN clause covers nine natural trigger phrases with genuine synonyms and phrasing variants a user would say: "create architecture diagram", "visualize Azure resources", "generate Mermaid diagram", "diagram my resources", "resource topology", "map Azure infrastructure". Coverage spans the concept space (diagram/visualize/map/show, resources/infrastructure/topology); no meaningful natural terms are missing (Azure resource groups have no file-extension analogue).

5 / 5

Distinctiveness Conflict Risk

Mostly distinct: Azure resource groups plus Mermaid output carve a clear niche, but triggers like "generate Mermaid diagram" and "architecture visualization" are not Azure-specific and could pull in generic diagramming skills — matching the 'mostly distinct; minor overlap risk' anchor. Not a 5 because two of the nine trigger phrases lack the Azure qualifier.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/azure-resource-visualizer/SKILL.md

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.