azure-compute
Azure VM and VMSS router for recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, capacity reservations, and Essential Machine Management. 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, essential machine management, EMM, machine enrollment.
72
87%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 solid skill description that excels at trigger term coverage and completeness, with an explicit WHEN clause containing a comprehensive list of natural keywords. Its main weakness is that the 'what' portion reads more like a list of topic categories rather than specific concrete actions the skill performs. The description is well-suited for skill selection among many options due to its distinctive Azure VM/VMSS focus and extensive trigger terms.
Suggestions
Replace category labels with concrete actions, e.g., instead of 'recommendations' say 'recommends VM sizes and families based on workload requirements'; instead of 'connectivity troubleshooting' say 'diagnoses and resolves VM connectivity issues including NSG rules, port access, and RDP/SSH failures'.
| 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, EMM), but these are category labels rather than concrete specific actions like 'extract text' or 'fill forms'. It tells you the topics but not exactly what it does with them. | 2 / 3 |
Completeness | The description clearly answers both 'what' (Azure VM and VMSS router for recommendations, pricing, autoscale, orchestration, connectivity troubleshooting, capacity reservations, and EMM) 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 both technical terms (VMSS, NSG, CRG, port 3389) and natural language terms (recommend, compare, server, website, burstable, black screen, reset password, reach VM, connect, refused). The breadth of keyword variations is strong. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Azure VM and VMSS topics with very specific trigger terms like 'VM family', 'VMSS', 'scale set', 'CRG', 'port 3389', 'NSG', and 'EMM'. This creates a distinct niche that is unlikely to conflict with non-Azure or non-VM 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 with good progressive disclosure. Its main weakness is redundancy — the routing logic is expressed three times (ASCII tree, signal table, workflows table) which inflates token usage without adding clarity. The actionability and workflow clarity are strong for a routing-type skill.
Suggestions
Consolidate the three routing representations (ASCII tree, signal table, workflows table) into a single comprehensive table to reduce redundancy and save tokens.
Trim the 'When to Use This Skill' section to remove overlap with the signal keywords already captured in the routing table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient as a routing document, but there is redundancy between the ASCII tree, the signal table, and the workflows table — all three convey largely the same routing information. The 'When to Use This Skill' section is also somewhat verbose with overlapping trigger descriptions. | 2 / 3 |
Actionability | For a routing skill, the actionability is high: it provides clear, specific signal-to-workflow mappings with direct file paths, a fallback disambiguation prompt for unclear intent, and an explicit routing rule about reading workflow files first. This is concrete, copy-paste-ready guidance for Claude. | 3 / 3 |
Workflow Clarity | The routing workflow is unambiguous with a clear decision tree, a signal-matching table, and an explicit fallback for unclear intent. The routing rule about reading the matched workflow file before accessing references adds an important sequencing constraint. For a routing skill (not a multi-step destructive operation), this is sufficient. | 3 / 3 |
Progressive Disclosure | The skill is structured as a clear overview/router that points to one-level-deep workflow files, each with their own reference files. Navigation is well-signaled with a dedicated table mapping workflows to their purposes and references. This is textbook progressive disclosure. | 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/github-copilot-for-azure
- Commit
915f809
- 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.