azure-deploy
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 excels across all dimensions. It provides specific concrete actions, comprehensive natural trigger terms, explicit when/when-not guidance, and clear differentiation from the related azure-prepare skill. The inclusion of both positive and negative trigger phrases is a best practice that minimizes conflict risk in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery.' Also specifies prerequisites like '.azure/deployment-plan.md' and 'validated status from azure-validate.' | 3 / 3 |
Completeness | Clearly answers both 'what' (execute Azure deployments for already-prepared apps, runs azd up/deploy/terraform apply with error recovery) and 'when' (explicit WHEN clause with trigger phrases, plus a DO NOT USE WHEN clause for disambiguation). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'run azd up', 'push to production', 'push to cloud', 'go live', 'ship it', 'bicep deploy', 'terraform apply', 'publish to Azure', 'launch on Azure'. These are highly natural phrases a user would actually type. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — explicitly differentiates itself from 'azure-prepare' with both positive triggers and negative triggers ('DO NOT use this skill when the user asks to CREATE a new application'). The DO NOT USE WHEN clause with specific phrases like 'create and deploy' and 'build and deploy' makes conflict resolution very clear. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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-organized deployment orchestration skill with excellent workflow clarity and progressive disclosure — it clearly sequences a complex multi-step deployment process with validation gates and delegates details to appropriate reference files. Its main weaknesses are redundant prerequisite warnings that consume tokens without adding value, and a lack of any inline executable examples (every concrete action is delegated to external files that weren't provided for evaluation).
Suggestions
Consolidate the prerequisite/validation warnings into a single concise block instead of repeating the same check in 4-5 different places throughout the document.
Include at least one inline executable command example (e.g., the basic `azd up` invocation with common flags) so the skill is partially actionable without loading external references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has significant redundancy in its prerequisite warnings — the same 'check validation status' message is repeated in the header callout, the stop block, the rules section, the steps table, and the validation proof check callout. The trigger/scope clarifications are useful but somewhat verbose. However, the steps table and reference links are efficiently structured. | 2 / 3 |
Actionability | The skill provides a clear step sequence and references specific tools and commands (azd up, azd deploy, terraform apply), but almost all concrete execution details are delegated to external reference files (recipes, checklists, troubleshooting). The skill itself contains no executable code or copy-paste-ready commands — it's essentially a routing document that tells Claude to go read other files for the actual instructions. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced with explicit validation checkpoints (plan check, pre-deploy checklist, RBAC health check, post-deploy verification, live role verification). Error handling is addressed in step 7 with recipe-specific error docs. The prerequisite gate pattern (prepare → validate → deploy) with explicit stop conditions is a strong feedback loop for preventing premature execution. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview/routing document with clear one-level-deep references to checklists, recipes, SDK docs, troubleshooting, and verification guides. References are clearly signaled with descriptive link text and organized by purpose (steps, SDK, MCP tools, general references). Navigation is straightforward. | 3 / 3 |
Total | 10 / 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
771a666
- 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.