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".
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-prepare90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 98%
↑ 1.24xAgent success when using this skill
Validation for skill structure
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 an excellent skill description that excels across all dimensions. It provides specific capabilities, extensive natural trigger terms, explicit when-to-use guidance with a dedicated WHEN clause, and clear differentiation from related skills through explicit exclusion criteria. The description effectively enables Claude to select this skill appropriately from a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Prepare Azure apps for deployment', 'infra Bicep/Terraform', 'azure.yaml', 'Dockerfiles', 'create/modernize', 'create+deploy'. The description clearly names specific technologies and actions. | 3 / 3 |
Completeness | Clearly answers both what (prepare Azure apps with Bicep/Terraform/Dockerfiles) and when (explicit 'WHEN:' clause with extensive trigger phrases). Also includes explicit exclusion guidance ('not cross-cloud migration'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases including 'create app', 'build web app', 'deploy to Azure', 'generate Terraform', 'function app', 'containerized Node.js app', 'todo list with frontend and API'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Azure-specific focus, explicit exclusion of cross-cloud migration pointing to alternative skill (azure-cloud-migrate), and specific technology stack (Bicep, Terraform, azure.yaml). Clear niche with minimal conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at workflow orchestration with clear phases, explicit validation gates, and well-organized progressive disclosure to reference materials. However, it suffers from verbose warning blocks that repeat the same message multiple times, and delegates nearly all concrete implementation details to external references, reducing standalone actionability.
Suggestions
Consolidate the multiple 'MANDATORY' and 'STOP' warnings into a single prominent section to reduce token overhead
Add at least one concrete inline example of what a minimal `.azure/plan.md` looks like rather than only referencing plan-template.md
Include a brief executable code snippet showing a common artifact (e.g., minimal azure.yaml or Bicep module) to improve standalone actionability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some redundancy with repeated warnings about plan-first workflow and mandatory compliance. The authoritative guidance header and multiple stop warnings add tokens without proportional value, though the core content is reasonably efficient. | 2 / 3 |
Actionability | The skill provides clear phase structures and references to detailed guides, but lacks concrete executable examples within the skill itself. Most actionable content is delegated to reference files rather than shown inline, making it dependent on external documents. | 2 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear phases (Planning → Execution), explicit blocking points ('STOP HERE'), numbered steps with references, and a defined handoff sequence (prepare → validate → deploy). Validation checkpoints are explicitly required before deployment. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview tables pointing to one-level-deep references. Content is appropriately split between the main skill (workflow orchestration) and reference files (detailed implementation). Navigation is clear with consistent linking patterns. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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.
- Reviewed
Table of Contents
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.