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.

Clearly answers both 'what' (executes Azure deployments for already-prepared applications, runs specific commands with error recovery) and 'when' (explicit WHEN clause with trigger phrases, plus explicit DO NOT USE WHEN clause for disambiguation).

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.

Exceptionally distinctive — explicitly differentiates itself from azure-prepare with both positive and negative trigger conditions. The 'DO NOT use this skill when...' and 'DO NOT USE WHEN' clauses with specific phrases like 'create and deploy' make it very unlikely to conflict with the preparation skill.

The skill has significant redundancy in its prerequisite warnings — the same 'check validation status' message is repeated in the header blockquote, the stop blockquote, the rules section, the steps table, and the validation proof check blockquote. The trigger/scope clarifications are useful but somewhat verbose. However, the core workflow table and references are efficient.

The skill provides a clear step sequence and references specific tools and commands (azd up, azd deploy, terraform apply), but almost all actual execution details are delegated to external reference files (recipes, checklists, troubleshooting). The skill itself contains no executable code or concrete command examples — it's essentially a routing document that tells you to look elsewhere for the real instructions.

The 10-step workflow table is clearly sequenced with explicit validation checkpoints (prerequisite check, pre-deploy checklist, RBAC health check, post-deploy verification, live role verification). Error handling is addressed in step 7, and there are clear feedback loops — if validation proof is missing, stop and re-validate. The prerequisite gate pattern is well-defined.

The skill is structured as a clear overview with well-signaled one-level-deep references to checklists, recipes, SDK docs, troubleshooting, and verification guides. Each step in the workflow table links to its relevant reference file. The SDK quick references and MCP tools tables provide easy navigation. Content is appropriately split between the overview and detailed reference files.