azure-validate
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment.
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
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 clearly defines its purpose (pre-deployment Azure validation), lists specific capabilities (configuration, infrastructure via Bicep/Terraform, permissions, prerequisites), and provides an extensive WHEN clause with natural trigger terms. The description is concise yet comprehensive, uses third-person voice correctly, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deep checks on configuration, infrastructure (Bicep or Terraform), permissions, and prerequisites before deploying.' These are concrete, actionable capabilities in a well-defined domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (pre-deployment validation covering configuration, infrastructure, permissions, prerequisites) and 'when' (explicit WHEN clause with extensive trigger phrases). The explicit trigger guidance is thorough. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'validate my app', 'check deployment readiness', 'run preflight checks', 'verify configuration', 'check if ready to deploy', 'validate azure.yaml', 'validate Bicep', 'test before deploying', 'troubleshoot deployment errors', 'validate Azure Functions', 'validate function app', 'validate serverless deployment'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Azure pre-deployment validation specifically, with distinct triggers like 'validate azure.yaml', 'validate Bicep', 'preflight checks'. This is a well-defined niche unlikely to conflict with general deployment or general Azure skills. | 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 is a well-structured orchestration skill with clear workflow sequencing, explicit validation gates, and good progressive disclosure to external references. Its main weaknesses are moderate redundancy in safety callouts and a lack of inline executable commands—the actual validation logic is entirely delegated to recipe references, making the skill less self-contained and actionable on its own.
Suggestions
Include at least one concrete inline example of a validation command with expected output (e.g., show what a successful `azd provision --preview` looks like) to improve actionability.
Consolidate the three separate callout boxes (prerequisite check, validation authority, mandatory next step) into a single constraints/rules section to reduce redundancy and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy—the mandatory next step callout, validation authority callout, and prerequisite check all repeat similar points about not skipping steps and not deploying without validation. The repeated emphasis on stopping and not proceeding adds tokens without proportional value. | 2 / 3 |
Actionability | The steps table provides a clear sequence but lacks concrete executable commands inline—it defers to external recipe references for the actual validation commands. Examples like 'azd provision --preview, bicep build, terraform validate' are mentioned in a callout but not structured as executable guidance with expected outputs. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, explicit validation checkpoints (run validation, build verification, record proof), a feedback loop (resolve errors before proceeding, re-run if failed), and a clear gate (only set Validated after all checks pass with proof). The prerequisite check and mandatory next step create a well-bounded process. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview with well-signaled one-level-deep references to recipes/README.md, global-rules.md, recipe-specific errors.md, and the deployment plan. Content is appropriately split between this overview and the referenced materials. | 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.
- Repository
- microsoft/azure-skills
- Commit
9d594ab
- 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.