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 well-crafted skill description that excels across all dimensions. It clearly specifies the validation actions performed, provides an explicit and comprehensive 'WHEN:' clause with natural trigger terms users would actually say, and maintains a distinct focus on Azure pre-deployment validation 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' - clearly describes what validation activities are performed. | 3 / 3 |
Completeness | Clearly answers both what ('Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure...') AND when (explicit 'WHEN:' clause with comprehensive trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'validate my app', 'check deployment readiness', 'run preflight checks', 'verify configuration', 'validate azure.yaml', 'validate Bicep', 'test before deploying', 'troubleshoot deployment errors', 'validate Azure Functions'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Azure pre-deployment validation with distinct triggers like 'azure.yaml', 'Bicep', 'Azure Functions' - unlikely to conflict with general deployment or other cloud provider 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 skill has excellent workflow clarity with clear sequencing, validation gates, and feedback loops for error recovery. However, it sacrifices actionability by delegating all concrete commands to external recipe files rather than providing inline examples. The multiple warning callouts, while important, create some redundancy that could be consolidated.
Suggestions
Add at least one concrete validation command example inline (e.g., show the actual azd provision --preview command with expected output) rather than only referencing external recipes
Consolidate the three warning callouts (prerequisite check, validation authority, mandatory next step) into a single workflow rules section to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy—the prerequisite check, validation authority, and mandatory next step callouts repeat similar information about workflow order and not skipping steps. The table format is efficient, but the multiple warning boxes add verbosity. | 2 / 3 |
Actionability | Steps reference external files (recipes, plan.md) rather than providing concrete commands inline. While it mentions 'azd provision --preview, bicep build, terraform validate' in a callout, the actual steps table says 'See recipe' without executable examples. The guidance is structured but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear numbered sequence with explicit validation checkpoints. The workflow includes a feedback loop (step 6: fix failures, re-run), proof recording requirement, and explicit gate (only set Validated after ALL checks pass). The prerequisite check and mandatory next step create clear boundaries. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear one-level-deep references to recipes/README.md, global-rules.md, and plan.md. Content is appropriately split—this skill focuses on the validation workflow while delegating specifics to referenced files. Navigation is clear with explicit file paths. | 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
1f4304b
- 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.