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.
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 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 is distinctive enough to avoid conflicts with other skills.
| 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
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 referenced materials. Its main weakness is low actionability — it delegates almost entirely to external references without providing any concrete commands or examples inline, making it hard for Claude to know exactly what to execute without reading multiple other files. Some redundancy in the callout blocks could be tightened.
Suggestions
Add at least one concrete inline example of a validation command (e.g., `azd provision --preview`, `az bicep build --file main.bicep`) so the skill is partially actionable without consulting references.
Consolidate the bottom callout about mandatory next step with step 9 in the table to reduce redundancy and save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy — the mandatory next step callout at the bottom repeats what step 9 already says, and the validation authority callout partially overlaps with step 6/8. The prerequisite check block is somewhat verbose but justified for safety. | 2 / 3 |
Actionability | Steps are listed but heavily delegate to external references (recipes/README.md, role-verification.md, deployment-plan.md) without providing any concrete commands or executable examples inline. The table format names actions but doesn't show what to actually run — e.g., 'Run Validation' just says 'Execute recipe-specific validation commands' without any concrete example. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit prerequisite checks, numbered steps, validation checkpoints (steps 5-6), error recovery (step 7 with re-validation loop), and a gate condition before status update (step 8). The validation authority callout reinforces the feedback loop of run → record → then proceed. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview with well-signaled one-level-deep references to recipes/README.md, role-verification.md, global-rules.md, and the deployment plan. Content is appropriately split between the orchestration steps here and detailed instructions in referenced files. | 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/github-copilot-for-azure
- Commit
a46a937
- 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.