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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured deployment skill with strong workflow sequencing, validation checkpoints, and clean progressive disclosure into a verified bundle. Weaker on conciseness (redundant emphasis/stop blocks) and actionability (the body leans on recipe references for executable detail).

Suggestions

Collapse the three repeated prerequisite/stop blocks (lines 12-32) into a single concise STOP-check section; the azure-prepare → azure-validate → azure-deploy chain only needs to be stated once.

Inline the most common deploy command sequence (e.g. a minimal azd up / azd deploy example) so the body is executable without opening a recipe, keeping recipes for advanced variants.

Trim capitalized emphasis ('MANDATORY COMPLIANCE', 'FORBIDDEN', 'DO NOT ASSUME / DO NOT SKIP') — state the rule once; repeated shouting adds tokens without adding information.

Dimension	Reasoning	Score
Conciseness	Mostly efficient (steps table, rules list) but padded with redundant emphasis blocks — the prerequisite is restated three times and 'AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE', 'FORBIDDEN', and multiple ⛔ STOP blocks repeat the same warning.	2 / 3
Actionability	Names concrete commands (azd provision --no-prompt, azd up, terraform apply) and exact MCP tools, but many steps defer to 'Follow recipe steps' / 'See recipe's errors.md' so the body alone is not copy-paste ready.	2 / 3
Workflow Clarity	A clear 10-step sequenced table with explicit validation checkpoints (Validated status + Validation Proof, pre-deploy checklist, RBAC health check, live role verification) and an error-recovery feedback loop for destructive deploy operations.	3 / 3
Progressive Disclosure	Overview body points to well-organized one-level-deep references (references/, recipes/<type>/, sdk/) with all cited paths verified to exist; content is appropriately split by recipe type with per-recipe README/errors/verify files.	3 / 3
	Total	10 / 12 Passed

Description

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.

A highly specific, third-person description that names exact commands, provides natural trigger phrases, and explicitly distinguishes itself from sibling skills via use/don't-use clauses. Its only weakness is verbosity — the prerequisite and redirect messaging is repeated heavily — but every dimension anchor is met.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery' and 'Execute Azure deployments' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (execute deployments via named commands) and when, with a 'WHEN:' clause and a 'DO NOT USE WHEN:' clause including redirects.	3 / 3
Trigger Term Quality	Broad coverage of natural phrases users would say: 'run azd up', 'push to production', 'go live', 'ship it', 'terraform apply', 'publish to Azure', 'launch on Azure'.	3 / 3
Distinctiveness Conflict Risk	Clear niche (deploy only, post-prepare/validate) with an explicit 'DO NOT USE WHEN' list redirecting creation tasks to azure-prepare, making conflict unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 10 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 10 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: microsoft/azure-skills
Commit: 2cd48ca

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.