azure-compute
Azure VM and VMSS router for recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, and capacity reservations. WHEN: Azure VM, VMSS, scale set, recommend, compare, server, website, burstable, lightweight, VM family, workload, GPU, learning, simulation, dev/test, backend, autoscale, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, connect, refused, Linux, black screen, reset password, reach VM, port 3389, NSG, troubleshoot, capacity reservation, CRG, reserve VMs, guarantee capacity, pre-provision capacity, CRG association, CRG disassociation.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 a strong skill description with excellent trigger term coverage and clear completeness via the explicit WHEN clause. Its main weakness is that the 'what' portion reads more as a list of topic areas rather than specific concrete actions Claude can perform. The extensive keyword list is well-suited for skill selection from a large pool.
Suggestions
Make the capability descriptions more action-oriented, e.g., 'Recommends VM sizes, estimates costs, troubleshoots connectivity issues, configures autoscale rules' instead of listing topic areas like 'recommendations, pricing, autoscale'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Azure VM and VMSS) and lists several action areas (recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, capacity reservations), but these are category-level rather than concrete specific actions like 'extract text' or 'fill forms'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Azure VM/VMSS router for recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, capacity reservations) and 'when' with an explicit 'WHEN:' clause containing extensive trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say, including specific scenarios ('black screen', 'reset password', 'port 3389', 'connect refused'), product terms ('VMSS', 'scale set', 'NSG', 'CRG'), and workload types ('GPU', 'burstable', 'dev/test', 'backend'). Very comprehensive keyword list. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused on Azure VM and VMSS specifically. The trigger terms are domain-specific enough (port 3389, NSG, CRG, VMSS, Flexible/Uniform orchestration) that it would be very unlikely to conflict with non-Azure skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 routing skill that clearly maps user intents to specific workflow files. Its main weakness is redundancy — the routing logic appears in three slightly different formats (tree, signal table, and workflows table), which wastes tokens without adding clarity. The progressive disclosure and actionability are strong, making this an effective entry point for Azure VM-related tasks.
Suggestions
Consolidate the routing tree diagram and the signal-to-workflow table into a single representation to reduce redundancy and save tokens.
The 'When to Use This Skill' bullet list overlaps significantly with the routing signals table — consider trimming it to only the high-level categories rather than listing specific keywords that are already in the routing table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has some redundancy — the routing logic is expressed three times (tree diagram, table, and workflows table) with overlapping information. The 'When to Use This Skill' section also partially duplicates the routing signals. | 2 / 3 |
Actionability | The routing is concrete and unambiguous — specific signal phrases map to specific workflow files with clear paths. The fallback for unclear intent provides an exact clarifying question to ask. For a routing skill, this is fully actionable. | 3 / 3 |
Workflow Clarity | The routing workflow is clearly sequenced: identify intent → match to workflow → read workflow file before references. The explicit routing rule about reading the matched workflow first is a good checkpoint. The fallback for ambiguous intent is well-defined. | 3 / 3 |
Progressive Disclosure | This is an excellent example of progressive disclosure — the SKILL.md serves as a concise routing overview with clear one-level-deep references to workflow files and their associated reference files. Navigation is well-signaled with both links and a summary table. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/azure-skills
- Commit
742d20b
- 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.