CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-resource-lookup

List, find, and show Azure resources across subscriptions or resource groups. Handles prompts like "list the websites in my subscription", "list my web apps", "show my app services", "list virtual machines", "list my VMs", "show storage accounts", "find container apps", and "what resources do I have". USE FOR: list websites, list web apps, list app services, show websites in subscription, resource inventory, find resources by tag, tag analysis, orphaned resource discovery (not for cost analysis), unattached disks, count resources by type, cross-subscription lookup, and Azure Resource Graph queries. DO NOT USE FOR: deploying/changing resources (use azure-deploy), cost optimization (use azure-cost), or non-Azure clouds.

68

Quality

81%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 covers all key dimensions thoroughly. It provides specific concrete actions, abundant natural trigger terms including common user phrasings, explicit USE FOR and DO NOT USE FOR guidance, and clear boundaries with other skills. The description is comprehensive without being unnecessarily verbose.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: list, find, and show Azure resources, with detailed examples like listing websites, web apps, virtual machines, storage accounts, container apps, finding resources by tag, orphaned resource discovery, unattached disks, count resources by type, cross-subscription lookup, and Azure Resource Graph queries.

3 / 3

Completeness

Clearly answers both 'what' (list, find, and show Azure resources across subscriptions or resource groups) and 'when' with explicit USE FOR and DO NOT USE FOR clauses, plus example prompts that serve as triggers. The DO NOT USE FOR section with skill redirects adds extra clarity.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'list websites', 'list my web apps', 'show my app services', 'list virtual machines', 'list my VMs', 'show storage accounts', 'find container apps', 'what resources do I have'. Includes both formal names and common abbreviations (VMs, app services).

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with explicit boundary-setting via DO NOT USE FOR clauses that redirect to specific other skills (azure-deploy for deploying, azure-cost for cost optimization). The focus on resource listing/discovery is clearly scoped and unlikely to conflict with deployment or cost analysis skills.

3 / 3

Total

12

/

12

Passed

Implementation

62%

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

This is a well-structured skill with a clear workflow and good error handling for Azure resource lookup. Its main weaknesses are the missing bundle reference file (azure-resource-graph.md) which would contain the most actionable content (KQL query patterns), and some verbosity in the 'When to Use' section that restates routing metadata. The routing table for dedicated MCP tools is a strong feature that adds genuine decision-making value.

Suggestions

Provide the referenced `references/azure-resource-graph.md` file with common KQL query patterns (e.g., list web apps, find orphaned disks, tag audit queries) to make the skill fully actionable.

Add 2-3 inline executable ARG query examples for the most common use cases (e.g., list all web apps, find unattached disks) so the skill is useful even without the reference file.

Trim the 'When to Use This Skill' section significantly — most of this is routing metadata that Claude doesn't need repeated in the body content.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary content like the 'When to Use This Skill' section which largely restates the description/routing metadata. The routing table and workflow are useful but the tip/warning callouts add moderate verbosity. The Quick Reference table duplicates information found elsewhere in the document.

2 / 3

Actionability

Provides concrete CLI commands and MCP tool invocations, but the primary action (Step 2) delegates to `extension_cli_generate` with a YAML snippet rather than providing executable ARG query examples. The referenced patterns file (azure-resource-graph.md) is missing from the bundle, so the actual KQL patterns that would make this fully actionable are absent.

2 / 3

Workflow Clarity

The three-step workflow is clearly sequenced: check for dedicated tool → generate ARG query → execute and format. The routing table provides an explicit decision point, error handling covers common failure modes with fixes, and constraints section provides clear guardrails. For a read-only lookup skill, validation checkpoints are less critical and the workflow is appropriately structured.

3 / 3

Progressive Disclosure

The skill references `references/azure-resource-graph.md` for common KQL patterns, which is good progressive disclosure design, but no bundle files are provided so this reference is broken. The inline content is reasonably structured with tables and sections, but the 'When to Use This Skill' section is overly long and could be trimmed, with detailed patterns offloaded to the missing reference file.

2 / 3

Total

9

/

12

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.

Validation11 / 11 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.