azure-deploy
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/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/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.
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-deploy88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 exemplary skill description that excels across all dimensions. It provides specific actions, comprehensive trigger terms covering both technical and casual language, explicit when/when-not guidance, and clear boundaries to prevent conflicts with the related azure-prepare skill. The description effectively enables Claude to make accurate skill selection decisions.
| 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/plan.md' and 'validated status from azure-validate'. | 3 / 3 |
Completeness | Clearly answers both what (execute Azure deployments, run specific commands) AND when (explicit WHEN clause with trigger phrases). Also includes explicit DO NOT USE WHEN guidance to prevent misuse. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'run azd up', 'push to production', 'go live', 'ship it', 'publish to Azure', 'launch on Azure'. Includes both technical commands and casual phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally clear niche with explicit boundary conditions. The DO NOT USE WHEN clause with specific phrases like 'create and deploy' and the directive to use 'azure-prepare instead' makes it highly distinguishable from related skills. | 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 skill has strong workflow clarity and progressive disclosure, with clear prerequisite checks and well-organized references. However, it suffers from redundant warning blocks that repeat the same prerequisite information multiple times, and delegates most actionable content to external files rather than providing inline examples. The skill would benefit from consolidating warnings and including at least one concrete deployment command example inline.
Suggestions
Consolidate the three separate prerequisite warning blocks into a single, concise prerequisite section to reduce redundancy
Add at least one inline executable example showing a complete azd up or azd deploy command with expected output
Consider moving the detailed validation proof check instructions to the referenced pre-deploy checklist rather than duplicating in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy with multiple warning boxes repeating the same prerequisite information (azure-validate must run first). The core workflow is reasonably efficient, but the repeated STOP warnings and prerequisite checks could be consolidated. | 2 / 3 |
Actionability | The skill provides a clear step table and references to specific commands (azd up, azd deploy, terraform apply), but lacks inline executable examples. Most concrete guidance is delegated to external references rather than shown directly. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit validation checkpoints (verify status = Validated, check Validation Proof section, pre-deploy checklist). The numbered steps table provides clear progression with error handling and verification steps included. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-organized reference links (SDK references, recipes, troubleshooting), and one-level-deep navigation. Content is appropriately split between the main skill and detailed reference files. | 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.
- 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.