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
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 purpose (pre-deployment Azure validation), lists specific capabilities (configuration, infrastructure, permissions, prerequisites checks), and provides an extensive explicit 'WHEN' clause with natural trigger terms. It uses proper third-person voice and is concise yet comprehensive.
| 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). Both dimensions are well-covered. | 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', and 'deployment readiness'. This is a well-defined niche unlikely to conflict with general Azure deployment or generic validation 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 excellent workflow clarity and progressive disclosure. Its main weakness is that the actual validation commands are deferred to external references rather than being shown inline, reducing immediate actionability. The content also has some redundancy across multiple warning callout blocks that could be consolidated.
Suggestions
Include 2-3 concrete example validation commands inline (e.g., exact `azd provision --preview`, `bicep build`, `terraform validate` invocations with typical arguments) rather than deferring entirely to recipe references.
Consolidate the three separate warning/callout blocks (prerequisite check, validation authority, mandatory next step) into a single concise rules section to reduce redundancy and token usage.
| 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 points. The multiple bold/emoji warning blocks add visual noise without proportional informational 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. The mention of 'azd provision --preview, bicep build, terraform validate' in the callout box is helpful but not structured as copy-paste-ready guidance. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, explicit validation checkpoints (step 3 build verification, step 5 resolve errors), a feedback loop (fix failures and re-run), and a clear gate condition (ALL checks must pass before setting status to Validated). The prerequisite check and mandatory next step are well-defined. | 3 / 3 |
Progressive Disclosure | Content is well-structured with a clear overview, a reference index table with 'when to load' guidance, and one-level-deep references to recipe docs, global rules, and preflight validation. The 'load on demand — do NOT read all at once' instruction is excellent progressive disclosure. | 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
- jonathan-vella/azure-agentic-infraops
- Commit
ec7b8ff
- 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.