CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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, actionable skill body with excellent progressive disclosure and a clear workflow. Its main weakness is redundancy: the meta-sections (Quality Standards, Always/Never Do, Output Format Specifications, Success Criteria) restate the core workflow and could be consolidated.

Suggestions

Consolidate the 'Quality Standards', 'Always Do/Never Do', and 'Success Criteria' sections into a single concise checklist to remove restatement of the workflow steps.

Merge the 'Output Format Specifications' Mermaid/markdown syntax into Step 3 and Step 4 respectively rather than repeating it as a separate section.

Add an explicit validate→fix→retry loop for Mermaid syntax (e.g., render-check the diagram before writing the final file) to strengthen the workflow's feedback checkpoint.

DimensionReasoningScore

Conciseness

The core 4-step workflow is efficient, but several later sections restate it — 'Quality Standards', 'Always Do/Never Do', 'Output Format Specifications', and 'Success Criteria' overlap the workflow and each other, so the body could be tightened noticeably.

3 / 5

Actionability

Provides concrete executable guidance — `az resource list --resource-group <name> --output json`, `az network vnet show ...`, MCP intent strings, Mermaid syntax patterns, and pointers to a complete example diagram and template — with only minor gaps since actual diagram content is necessarily generated from discovered resources.

4 / 5

Workflow Clarity

A clear 4-step sequence (select group → discover/analyze → construct diagram → create file) with checkpoints ('validate it exists', 'Verify all resource details', 'test syntax mentally') and edge-case handling, though it lacks an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview and splits detail into well-signaled, one-level-deep bundle files — references/azure-resource-graph.md, assets/example-diagram.md, assets/template-architecture.md — all referenced in the body and verified to exist.

5 / 5

Total

16

/

20

Passed

Description

95%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, third-person description that clearly states what the skill does and when to use it, with a rich set of natural trigger phrases. Minor specificity gaps (omitting the markdown documentation output) keep it just below a perfect specificity score.

DimensionReasoningScore

Specificity

Names the Azure domain and lists concrete actions — 'Analyze Azure resource groups', 'generate detailed Mermaid architecture diagrams', 'showing the relationships between individual resources' — with only minor coverage gaps (e.g., the produced markdown docs are not mentioned in the description).

4 / 5

Completeness

It explicitly answers both 'what' (analyze resource groups and generate Mermaid diagrams showing relationships) and 'when' (a WHEN: clause with concrete trigger phrases), matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The WHEN clause gives broad, natural trigger coverage with synonyms — 'create architecture diagram', 'visualize Azure resources', 'diagram my resources', 'map Azure infrastructure', 'architecture visualization', 'resource topology' — phrases a user would genuinely say.

5 / 5

Distinctiveness Conflict Risk

The niche is distinct and specific to Azure resource-group architecture visualization, with trigger terms unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/azure-skills
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.