azure-validate
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity 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, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 scope (Azure pre-deployment validation), lists specific concrete capabilities (configuration checks, Bicep/Terraform infrastructure validation, RBAC, managed identity), and provides an extensive explicit WHEN clause with natural trigger terms. The description is well-structured, uses third person voice, and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying.' These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (pre-deployment validation covering configuration, infrastructure, RBAC, managed identity, prerequisites) and 'when' with an explicit 'WHEN:' clause listing numerous trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'validate my app', 'check deployment readiness', 'run preflight checks', 'validate azure.yaml', 'validate Bicep', 'troubleshoot deployment errors', 'verify RBAC roles', 'check role assignments', 'what-if analysis', and many more variations covering different user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Azure pre-deployment validation specifically, with distinct triggers like 'azure.yaml', 'Bicep', 'RBAC roles', 'managed identity permissions', and 'Container Apps deployment' that are unlikely to conflict with general deployment or non-Azure skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a well-structured validation workflow with clear sequencing and appropriate gates, but relies heavily on external references for the actual executable content. The repeated warning callouts add verbosity without proportional value. The skill would benefit significantly from including at least the key validation commands inline rather than deferring everything to recipe files.
Suggestions
Include the most common validation commands inline (e.g., `azd provision --preview`, `bicep build`, `terraform validate`) rather than only referencing them in the callout—this would make the skill immediately actionable.
Consolidate the three separate warning/authority callouts into a single concise constraints section to reduce redundancy and save tokens.
Add a concrete example of what a completed 'Section 7: Validation Proof' entry should look like, so Claude knows the expected output format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but has some redundancy—the prerequisite check, validation authority callout, and mandatory next step callout all repeat similar points about not deploying without validation. The repeated warnings and emphasis blocks add tokens without proportional value. | 2 / 3 |
Actionability | Steps are listed but lack concrete executable commands inline—most actions say 'see recipe' or reference external files. There are no actual validation commands shown (e.g., `azd provision --preview`, `bicep build`) despite mentioning them in the callout. The skill describes what to do rather than providing copy-paste ready instructions. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, explicit validation checkpoints (steps 3-5), error resolution (step 7), a gate before status update (step 8), and a feedback loop (fix and re-run). The validation authority callout reinforces that proof must be recorded before proceeding. | 3 / 3 |
Progressive Disclosure | References to external files like recipes/README.md, role-verification.md, and global-rules.md are well-signaled and appear to be one level deep. However, since no bundle files were provided, we cannot verify these references exist. The deployment plan file is referenced repeatedly as both input and output, which is clear but the actual recipe content that drives most steps is entirely external. | 2 / 3 |
Total | 9 / 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
d02fd24
- 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.