Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Azure Compute Skill; When to Use This Skill; Routing.
File analysis
File analysis: besides SKILL.md, the body references references/. Those resources load on demand.
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Ask your Agent to install
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "azure-compute" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-506944e004e00f0b-Azure-Compute.html
Save it as .cursor/skills/azure-compute/SKILL.md or .claude/skills/azure-compute/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/microsoft/azure-skills instead of creating only a SKILL.md.
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Routes Azure VM and Virtual Machine Scale Set (VMSS) requests to the right workflow.
When to Use This Skill
User wants to recommend, compare, or price a VM or VMSS
User wants to create, provision, or deploy a VM or VMSS
User asks about Capacity Reservation Groups (CRG) — reserve, guarantee capacity, pre-provision
User asks about Essential Machine Management (EMM) — machine enrollment, monitor
Disambiguate with azure-prepare: if the user wants to deploy an application (Docker service, web app, API, serverless workload), route to azure-prepare. vm-creator is for bare VM/VMSS infrastructure only.
Routing
Mandatory workflow-first routing: never route directly to references/* files. First classify the user intent below, open the matched workflow file, then load only the reference files that workflow requests. Reference files are supporting material, not entry points. If the intent is unclear, ask a clarifying question to disambiguate between the workflows.
| Workflow | File | Use when |
|---|---|---|
| VM Recommender | vm-recommender.md | User asks which VM/VMSS to choose, whether to use VMSS/autoscaling, wants pricing, or wants to compare options |
| VM Creator | vm-creator.md | User wants to create, provision, or deploy a bare VM or VMSS (not an app deployment) |
| Capacity Reservation | capacity-reservation.md | User needs to reserve / guarantee VM capacity (CRG create / associate / disassociate) |
| Essential Machine Management | essential-machine-management.md | User asks about EMM / machine enrollment / monitor |