Lists multiple specific concrete actions: list, find, and show Azure resources, orphaned resource discovery, unattached disks, count resources by type, cross-subscription lookup, Azure Resource Graph queries, find resources by tag, and tag analysis.

Clearly answers both 'what' (list, find, show Azure resources across subscriptions/resource groups, tag analysis, orphaned resource discovery, etc.) and 'when' with explicit USE FOR and DO NOT USE FOR clauses that provide clear trigger guidance and boundary conditions.

Excellent coverage of natural user terms including common variations: 'list websites', 'list web apps', 'list app services', 'show my VMs', 'list virtual machines', 'show storage accounts', 'find container apps', 'what resources do I have'. These are phrases users would naturally say.

Highly distinctive with explicit boundary-setting via DO NOT USE FOR clauses that reference specific alternative skills (azure-deploy for deploying, azure-cost for cost optimization). The focus on listing/finding/showing resources is a clear niche distinct from deployment or cost analysis.

The skill is mostly efficient but includes some unnecessary content like the 'When to Use This Skill' section which largely restates the description/frontmatter, and the routing table is quite extensive. The tip/warning callouts add some value but the overall document could be tightened by ~30%.

Provides concrete CLI commands and MCP tool invocations, but the core workflow relies on `extension_cli_generate` to produce the actual query rather than giving executable ARG query examples directly. The YAML block for MCP invocation is helpful but the skill lacks complete copy-paste-ready KQL examples for common scenarios (those are deferred to a reference file that doesn't exist in the bundle).

The 3-step workflow is clearly sequenced (check dedicated tool → generate ARG query → execute and format), but there are no validation checkpoints or feedback loops. If a query returns empty results or errors, the error handling table lists fixes but there's no explicit 'verify → fix → retry' loop integrated into the workflow steps.

References `references/azure-resource-graph.md` for query patterns which is good progressive disclosure design, but no bundle files are provided, meaning the reference doesn't actually exist. The main file also includes substantial inline content (routing table, error table) that could potentially be split out, though for a skill of this size it's borderline acceptable.