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/azure-skills --skill azure-prepare90
Quality
85%
Does it follow best practices?
Impact
98%
1.48xAverage score across 3 eval scenarios
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 an excellent skill description that hits all the key criteria. It provides specific capabilities, extensive natural trigger terms, explicit 'WHEN' guidance, and even clarifies boundaries with related skills. The description is comprehensive without being padded with fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Prepare Azure apps for deployment', 'infra Bicep/Terraform', 'azure.yaml', 'Dockerfiles', 'create/modernize', 'add authentication', 'add caching'. Covers infrastructure, configuration, and deployment artifacts. | 3 / 3 |
Completeness | Clearly answers WHAT (prepare Azure apps, generate Bicep/Terraform, Dockerfiles) and WHEN with explicit 'WHEN:' clause containing extensive trigger phrases. Also clarifies scope boundaries ('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'. Includes both technical terms and casual user language. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from 'azure-cloud-migrate' skill, focuses specifically on Azure deployment preparation, and uses Azure-specific terminology (Bicep, azure.yaml, Azure Container Apps, Azure App Service) that creates a clear niche. | 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 checkpoints, and good progressive disclosure through reference files. However, it suffers from excessive warning/emphasis formatting that adds token overhead, and the main document lacks inline executable examples, delegating most concrete guidance to references.
Suggestions
Remove or significantly reduce the 'AUTHORITATIVE GUIDANCE' preamble and repeated MANDATORY/STOP warnings - Claude doesn't need this emphasis and it wastes tokens
Add at least one concrete inline example of what a minimal `.azure/plan.md` looks like rather than only referencing plan-template.md
Consider adding a brief executable code snippet showing a simple artifact generation (e.g., minimal azure.yaml or Bicep snippet) to improve actionability
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some redundancy with repeated warnings (MANDATORY, STOP, etc.) and the authoritative guidance preamble is unnecessary for Claude. However, the core content is reasonably efficient with good use of tables and references. | 2 / 3 |
Actionability | The skill provides clear workflow steps and references to detailed guides, but lacks concrete executable examples within the main document. Most actionable content is delegated to reference files rather than shown inline. | 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 checkpoint is 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.