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.
85
81%
Does it follow best practices?
Impact
Pending
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', 'Container Apps deployment'. This is a well-defined niche unlikely to conflict with general deployment or general 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.
This skill provides a well-structured validation workflow with clear sequencing and explicit gates, but relies heavily on external references for actual executable guidance. The repeated warning callouts about not deploying without validation add redundancy. The skill would benefit from including key validation commands inline rather than deferring almost everything to recipe files.
Suggestions
Include the most common validation commands inline (e.g., `azd provision --preview`, `bicep build`, `terraform validate`) with expected output patterns, rather than deferring entirely to recipe references.
Consolidate the three separate warning callouts (prerequisite check, validation authority, mandatory next step) into a single concise constraints section to reduce redundancy.
Add a brief example of what a completed 'Section 7: Validation Proof' entry should look like to make the proof-recording step more actionable.
| 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. The table provides a clear sequence but the actual validation commands (azd provision --preview, bicep build, etc.) are only mentioned in a callout box rather than being integrated into the workflow steps with full syntax. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, explicit validation checkpoints (step 3-4), a proof-recording step (step 6), error resolution before proceeding (step 7), and a clear gate before status update (step 8). The feedback loop of fix-then-revalidate is explicitly stated in the closing callout. | 3 / 3 |
Progressive Disclosure | References to external files (recipes/README.md, role-verification.md, global-rules.md, deployment-plan.md) are present and one-level deep, which is good. However, no bundle files were provided to verify these references exist, and the skill heavily depends on external content for actual execution details, making it hard to evaluate completeness. The inline content could better summarize what each reference provides. | 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/github-copilot-for-azure
- Commit
771a666
- 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.