azure-resource-visualizer

Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. USE FOR: 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 DO NOT USE FOR: creating/modifying resources (use azure-deploy), security scanning (use azure-security), performance troubleshooting (use azure-diagnostics), code generation (use relevant service skill)

Quality

71%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/skills/azure-resource-visualizer/SKILL.md

Quality

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 an excellent skill description that clearly defines its scope, provides abundant natural trigger terms, and explicitly addresses both when to use and when not to use the skill. The DO NOT USE FOR section with references to alternative skills is particularly effective for disambiguation. The description uses proper third-person voice throughout.

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 USE FOR and DO NOT USE FOR clauses with specific trigger scenarios and boundary conditions).	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 are highly natural phrases.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche (Azure resource group analysis + Mermaid diagram generation). The DO NOT USE FOR section explicitly delineates boundaries against related skills like azure-deploy, azure-security, and azure-diagnostics, greatly reducing conflict risk.	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 progressive disclosure with well-signaled external references. However, it is significantly over-verbose, restating obvious expectations and including motivational language that wastes tokens. Actionability is moderate — it provides useful patterns but lacks complete executable examples inline, and the workflow lacks proper validation checkpoints for diagram generation.

Suggestions

Cut 'Core Responsibilities', 'Quality Standards', 'Success Criteria', and the closing motivational sentence — these restate what's already implicit in the workflow steps and add ~40 lines of token waste.

Consolidate the 'Always Do' / 'Never Do' lists into the workflow steps where they're relevant, keeping only the non-obvious constraints (e.g., read-only analysis, wait for user selection).

Add an explicit Mermaid syntax validation step in the workflow (e.g., a regex check or structural validation command) rather than 'test syntax mentally before output'.

Include a small but complete inline Mermaid diagram example (3-5 nodes) rather than only deferring to an external example file, so the skill is actionable without loading references.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with significant padding. Sections like 'Core Responsibilities', 'Quality Standards', 'Success Criteria', and 'Constraints & Boundaries' largely restate obvious expectations Claude already knows (e.g., 'Accuracy: Verify all resource details', 'Don't omit resources'). The 'Never Do' and 'Always Do' checklists are largely redundant with the workflow steps. The motivational closing sentence is unnecessary.	1 / 3
Actionability	Provides some concrete guidance like specific az CLI commands and Mermaid syntax patterns, but lacks executable code examples. The tool usage patterns are described abstractly (e.g., 'Use intent="list resource groups"') rather than with complete, copy-paste-ready examples. The diagram construction section describes conventions but doesn't show a complete inline example (it defers to an external file).	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 — no 'validate Mermaid syntax' step, no feedback loop for handling incorrect resource relationships, and 'test syntax mentally before output' is not a real validation step. For a multi-step process involving file creation, this is a gap.	2 / 3
Progressive Disclosure	Good structure with clear references to external files (azure-resource-graph.md, example-diagram.md, template-architecture.md) that are one level deep and well-signaled with context about when to load them. The reference index table at the bottom is a nice touch for on-demand loading.	3 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jonathan-vella/azure-agentic-infraops
Commit: ec7b8ff

Reviewed: 7 days 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.