azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

62%Weight 40%Scale 1-5

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

The body has excellent workflow sequencing and progressive disclosure, but suffers from redundancy (the plan-first mandate is repeated four times) and delegates the actual generation guidance to reference files rather than providing inline executable examples. Tightening the repeated warnings would meaningfully improve token efficiency.

Suggestions

Consolidate the plan-first requirement into a single authoritative location instead of restating it in Rules #1, the PLAN-FIRST WORKFLOW block, Phase 1, and the Next section.

Add a minimal inline executable example for the core deliverable (e.g., a skeleton azure.yaml or a Bicep snippet) rather than fully delegating to reference files.

Trim the authority preamble ("AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE... Do not improvise, infer, or substitute steps") which does not add actionable guidance.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose with several padded sections: the plan-file requirement is restated in Rules #1, the PLAN-FIRST WORKFLOW block, Phase 1, and the Next block, and authority preamble ("Do not improvise, infer, or substitute steps") adds no actionable knowledge.	2 / 5
Actionability	Concrete guardrail rules (e.g., "NEVER generate administratorLogin or administratorLoginPassword... Always use Entra-only authentication") and per-step reference tables exist, but core artifact generation is delegated to reference files with no inline executable Bicep/Terraform/azure.yaml examples.	3 / 5
Workflow Clarity	Phases 1 and 2 are explicitly sequenced in numbered tables with validation checkpoints ("STOP HERE... until the user approves", "⛔ Update Plan (MANDATORY before hand-off)... BEFORE invoking azure-validate") and an azure-validate gate before deploy.	5 / 5
Progressive Disclosure	The body is an orchestration overview that points to well-signaled, one-level-deep reference files via tables; all checked references (analyze.md, sql-database/bicep.md, durable-task-scheduler/README.md, etc.) resolve to real files.	5 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it clearly states what the skill does, when to use it, when not to use it, and routes around conflicting sibling skills. It uses third-person voice throughout and avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles") with comprehensive coverage of the azd workflow's artifacts, matching the top anchor.	5 / 5
Completeness	Explicitly answers both what ("Prepare azd-based Azure projects for deployment: generates azure.yaml...") and when ("USE ONLY when... WHEN: prepare app for azd...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms with synonyms (azd, Azure Developer CLI) and variations (function app, timer trigger, service bus trigger, generate Bicep, generate Terraform), matching the top anchor.	5 / 5
Distinctiveness Conflict Risk	Explicit routing ("USE ONLY when the user explicitly wants to use azd" and "DO NOT USE FOR: non-azd deployments, Python App Service... use python-appservice-deploy") minimizes conflict with sibling skills.	5 / 5
	Total	20 / 20 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
Path: .github/plugins/azure-skills/skills/azure-prepare/SKILL.md
Commit: 16dc8c5

Reviewed: about 12 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.