AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-compute

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, capacity reservation (CRG), reserve, guarantee capacity, pre-provision, CRG association, CRG disassociation, machine enrollment (EMM), Essential Machine Management, monitor. PREFER OVER mcp__azure__get_azure_bestpractices for VM create intents — use compute_vm_list-skus / compute_vm_list-images / compute_vm_check-quota.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-compute at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 37

workflows/vm-recommender/references/handoff-to-creator.md

Hand-off to vm-creator

When the user wants to provision the recommended option (not just compare), hand off to vm-creator. Don't skip directly to an output adapter — the user must see and approve the Plan Card first.

Required before hand-off

Render the Plan Card markdown table in chat with the chosen SKU, region, instance count, pricing, and quota status pre-filled from the recommender's work. The user is approving the Plan Card, not the artifact.

Routing signals

| User says | Action | |---|---| | "let's create it" / "spin one up" / "deploy this" | Render Plan Card → route to vm-creator Step 5 with selected SKU + region pre-filled | | "give me the az CLI / Bicep / Terraform" | Render Plan Card → route to vm-creator Step 6 (Output Choice) | | "just compare prices" / "I'm still deciding" | Stay in vm-recommender; offer to revisit |

Example hand-off message

"Want me to generate the create command? I can output az CLI, Bicep, Terraform, or apply it via Azure MCP — I'll carry over the SKU, region, and pricing we just landed on."

What carries over

| Recommender output | Plan Card row | |---|---| | Hosting Model (VM vs VMSS) | Hosting model | | VM Size (ARM SKU) | Size | | Region | Region | | Instance Count (or min–max) | Instance count (VMSS only) | | Estimated $/hr | Estimated cost | | Quota Status (✅/⚠️/❌) | Quota |

vm-creator Steps 2–4 (Depth Probe, Adaptive Gather, Validate) still run after hand-off to fill in OS, auth, networking, and tagging — they're additive on top of the recommender's spec choice.