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.

80

Quality

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugin/skills/azure-resource-lookup/SKILL.md
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 dimensions thoroughly. It provides specific concrete actions, abundant natural trigger terms that users would actually say, explicit 'USE FOR' and 'DO NOT USE FOR' clauses that clearly delineate scope, and distinct boundaries referencing alternative skills to minimize conflict risk. The description uses proper third-person voice throughout.

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 that provide detailed trigger guidance and boundary conditions with references to alternative skills.

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 clear boundaries: explicitly states DO NOT USE FOR deploying/changing resources (use azure-deploy), cost optimization (use azure-cost), or non-Azure clouds. This creates a clear niche focused on read-only Azure resource inventory and discovery.

3 / 3

Total

12

/

12

Passed

Implementation

50%

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

This is a competent skill that provides useful routing logic and a clear workflow structure for Azure resource lookup. Its main weaknesses are the lack of concrete, executable KQL query examples inline (relying instead on a missing reference file), the absence of validation checkpoints in the workflow, and some verbosity in the 'When to Use' section that restates information Claude could infer.

Suggestions

Add 2-3 complete, executable KQL query examples inline (e.g., list all web apps, find unattached disks, tag audit) rather than relying solely on the missing references/azure-resource-graph.md file.

Add a validation checkpoint after Step 3 — e.g., 'Verify results are non-empty; if empty, check subscription scope and resource type spelling before reporting to user.'

Trim the 'When to Use This Skill' section to 3-4 key bullets — Claude can infer most of these use cases from the skill title and quick reference.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary content. The 'When to Use This Skill' section is overly verbose with many bullet points that largely restate the description. The routing table is useful but could be more compact. The warning/tip callouts add value but the overall document could be tightened.

2 / 3

Actionability

Provides concrete tool names, CLI commands, and a routing table, but the core workflow relies on `extension_cli_generate` which abstracts away the actual query construction. The bash example for formatting is helpful, but there are no complete executable KQL query examples — the referenced patterns file (azure-resource-graph.md) is not provided in the bundle.

2 / 3

Workflow Clarity

The 3-step workflow is clearly sequenced (check dedicated tool → generate ARG query → execute and format), and the routing table aids decision-making. However, there are no validation checkpoints — no step to verify results are correct, handle empty results gracefully, or confirm the generated query before execution. The error handling table partially compensates but isn't integrated into the workflow steps.

2 / 3

Progressive Disclosure

The skill references 'references/azure-resource-graph.md' for common KQL patterns, which is good progressive disclosure design. However, no bundle files are provided, meaning this reference is broken/unverifiable. The inline content is reasonably structured with tables and sections, but the routing table and 'When to Use' section could arguably be split out to keep the main skill leaner.

2 / 3

Total

8

/

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/github-copilot-for-azure
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.