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). WHEN: "create app", "build web app", "create API", "create serverless HTTP API", "create frontend", "create back end", "build a service", "modernize application", "update application", "add authentication", "add caching", "host on Azure", "create and deploy", "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", "deploy to Azure Container Apps using Terraform", "generate Terraform", "generate Bicep", "function app", "timer trigger", "service bus trigger", "event-driven function", "containerized Node.js app", "social media app", "static portfolio website", "todo list with frontend and API", "prepare my Azure application to use Key Vault", "managed identity".

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Failed to scan

The risk profile of this skill

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugin/skills/azure-prepare/SKILL.md

Quality

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 a strong skill description that excels across all dimensions. It provides specific capabilities, extensive natural trigger terms, clear what/when guidance, and explicit boundaries to avoid conflicts with related skills. The negative boundary directing cross-cloud migration to another skill is a particularly effective touch for disambiguation.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Prepare Azure apps for deployment', 'infra Bicep/Terraform', 'azure.yaml', 'Dockerfiles', and distinguishes create/modernize from cross-cloud migration. Covers specific technologies and artifact types.	3 / 3
Completeness	Clearly answers both 'what' (prepare Azure apps for deployment with Bicep/Terraform, azure.yaml, Dockerfiles) and 'when' with an explicit and extensive WHEN clause listing numerous trigger phrases. Also includes a negative boundary ('not cross-cloud migration') with a redirect to the correct skill.	3 / 3
Trigger Term Quality	Excellent coverage of natural user phrases including 'create app', 'build web app', 'deploy to Azure', 'generate Terraform', 'generate Bicep', 'function app', 'containerized Node.js app', 'static portfolio website', 'todo list with frontend and API', and many more variations users would naturally say.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with clear Azure-specific scope, explicit boundary against cross-cloud migration (directing to 'azure-cloud-migrate'), and specific technology triggers like Bicep, Terraform, Azure App Service, Azure Container Apps that clearly delineate its niche.	3 / 3
	Total	12 / 12 Passed

Implementation

54%

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

The skill has excellent workflow structure and progressive disclosure, with clear phased execution, validation gates, and well-organized references to detailed sub-documents. However, it is severely undermined by extreme verbosity and repetition — the same critical instructions (plan file creation, validation hand-off) are restated 4-8 times each, wasting significant token budget. Actionability is moderate since nearly all concrete implementation is deferred to reference files with no inline examples.

Suggestions

Consolidate repeated instructions: the plan-file creation requirement appears ~8 times and the azure-validate hand-off ~4 times. State each critical rule once in a prominent location and reference it elsewhere instead of restating it verbatim.

Remove the authoritative compliance preamble — Claude follows skill instructions by design; the 'IGNORE prior training' framing wastes tokens and adds no behavioral value.

Add at least one concrete inline example, such as a minimal deployment-plan.md skeleton or a sample azure.yaml, to improve actionability without requiring reference file lookups.

Reduce emoji/symbol markers (⛔, ❌, ⚠️) to key locations only — overuse dilutes their signaling value and adds visual noise.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and repetitive. The same instructions are restated multiple times (e.g., 'create deployment-plan.md' is repeated ~8 times with nearly identical warnings, the mandatory hand-off to azure-validate is stated 4+ times). The authoritative compliance preamble and excessive ⛔/❌ markers add significant token bloat without new information. Claude doesn't need to be told the same critical instruction 5 different ways.	1 / 3
Actionability	The skill provides a structured workflow with specific file paths and tool references, but almost all actual implementation details are deferred to external reference files. There are no concrete code examples, no executable commands (beyond file names), and no inline templates. The skill is more of a routing/orchestration document than an actionable guide.	2 / 3
Workflow Clarity	The multi-phase workflow is clearly sequenced with explicit blocking gates (Phase 1 must complete before Phase 2), validation checkpoints (azure-validate before azure-deploy), mandatory status updates, and user approval gates. Error recovery is addressed through the validate→fix→retry pattern and destructive action confirmations.	3 / 3
Progressive Disclosure	Content is well-structured as an overview that delegates to clearly signaled one-level-deep references (e.g., references/analyze.md, references/requirements.md, references/security.md). The main file serves as a routing hub with tables linking steps to reference documents, and SDK quick references are cleanly organized.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/github-copilot-for-azure
Commit: a46a937

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