azure-prepare

Prepare Azure apps for deployment (infra Bicep/Terraform, azure.yaml, Dockerfiles). Use for create/modernize or create+deploy; not cross-cloud migration (use azure-cloud-migrate). DO NOT USE FOR: copilot-sdk apps (use azure-hosted-copilot-sdk), or Python code-only App Service deploys (use python-appservice-deploy). WHEN: "create app", "build web app", "create API", "modernize application", "host on Azure", "deploy to Azure", "deploy to Azure using Terraform", "deploy to Azure App Service", "deploy to Azure App Service using Terraform", "deploy to Azure Container Apps", "generate Terraform", "generate Bicep", "function app", "timer trigger", "service bus trigger", "event-driven function", "managed identity".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

85%

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

A well-structured orchestration skill with a clear phased workflow, concrete actionable guidance, and excellent progressive disclosure through real, well-signaled reference files. Its main weakness is verbosity from repeating the plan-file and workflow mandates across multiple sections.

Suggestions

Consolidate the `.azure/deployment-plan.md` requirement: state it once in Rules and once in the PLAN-FIRST section, then have Phase 1 Step 6, Phase 2 Step 6, and the Next section reference it rather than re-stating the full mandate each time.

Remove or shrink the opening "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" block — it is meta-commentary about compliance rather than actionable preparation guidance.

Reduce redundant emphasis markers (⛔/❌/MANDATORY caps) on the plan-file and hand-off steps where the same instruction already appears; keep one strong statement per requirement.

Dimension	Reasoning	Score
Conciseness	Mostly task-focused and free of basic-concept explanation, but the plan-file mandate and the azure-prepare → azure-validate → azure-deploy workflow are repeated across Rules, the PLAN-FIRST section, Phase 1 Step 6, Phase 2 Steps 6–7, and the Next section, and the opening "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" block is meta-padding that could be trimmed.	2 / 3
Actionability	Concrete, specific guidance throughout: exact filenames (`.azure/deployment-plan.md`), named commands to run or avoid (`azd init -t`, `azd up`, `terraform apply`), explicit skill invocations, and routing tables mapping prompt keywords/codebase markers to specific skills — actionable for an instruction-only orchestration skill.	3 / 3
Workflow Clarity	Clearly sequenced Phase 1 (BLOCKING planning) → Phase 2 (execution) → Next (validate→deploy) with numbered tables, explicit approval/verification checkpoints ("STOP HERE" before Phase 2, Functional Verification, mandatory plan-status update before hand-off), and a stated validate→deploy feedback gate.	3 / 3
Progressive Disclosure	The body is an overview that points to ~163 well-organized, one-level-deep reference files via clearly signaled links in reference-table columns; spot-checked referenced paths (azure-context, global-rules, sql-database/bicep, specialized-routing, durable, sdk/*) all resolve to real files, and detailed per-service content is appropriately split out.	3 / 3
	Total	11 / 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 strong, specific description that states concrete outputs, provides a rich set of natural trigger terms, answers both what and when, and proactively disambiguates from sibling Azure skills via explicit DO NOT USE FOR routing.

Dimension	Reasoning	Score
Specificity	Names concrete deliverables — "infra Bicep/Terraform, azure.yaml, Dockerfiles" — listing multiple specific preparation actions rather than vague language; uses third person ("Prepare Azure apps for deployment").	3 / 3
Completeness	Explicitly answers what ("Prepare Azure apps for deployment (infra Bicep/Terraform, azure.yaml, Dockerfiles)") and when ("Use for create/modernize or create+deploy" plus a WHEN trigger list), satisfying both halves.	3 / 3
Trigger Term Quality	The WHEN clause covers natural user phrasings users would actually say ("create app", "build web app", "host on Azure", "deploy to Azure Container Apps", "function app", "timer trigger", "managed identity") with good breadth.	3 / 3
Distinctiveness Conflict Risk	Actively disambiguates with a DO NOT USE FOR carve-out routing cross-cloud migration, copilot-sdk apps, and Python App Service deploys to sibling skills, giving it a clear niche unlikely to trigger the wrong skill.	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: 12 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 13 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.