azure-validate
**WORKFLOW SKILL** — Pre-deployment validation for Azure: config, infrastructure (Bicep/Terraform), permissions, prerequisites. WHEN: 'validate my app', 'check deployment readiness', 'run preflight checks', 'validate azure.yaml', 'validate Bicep', 'test before deploying', 'validate Azure Functions'. DO NOT USE FOR: post-deploy troubleshooting (azure-diagnostics), executing deploys (azure-deploy).
75
92%
Does it follow best practices?
Impact
—
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 an excellent skill description that hits all the marks. It clearly defines the scope (pre-deployment Azure validation), provides rich natural trigger terms, and explicitly delineates boundaries with related skills to prevent conflicts. The structured format with WHEN and DO NOT USE FOR clauses makes it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: config validation, infrastructure validation (Bicep/Terraform), permissions checking, and prerequisites validation. Also specifies the domain clearly as Azure pre-deployment. | 3 / 3 |
Completeness | Clearly answers both 'what' (pre-deployment validation for Azure covering config, infrastructure, permissions, prerequisites) and 'when' (explicit WHEN clause with multiple trigger phrases). Also includes a helpful 'DO NOT USE FOR' clause that further clarifies boundaries. | 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', 'test before deploying', 'validate Azure Functions'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting via the 'DO NOT USE FOR' clause, distinguishing it from azure-diagnostics (post-deploy) and azure-deploy (executing deploys). The pre-deployment validation niche is clearly carved out. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 workflow skill with clear sequencing, concrete commands, explicit validation checkpoints, and good progressive disclosure through on-demand reference loading. Its main weakness is moderate verbosity from redundant warning callouts that repeat information already present in the steps table, consuming extra tokens without adding new information. Overall it's a strong skill that effectively guides Claude through pre-deployment validation.
Suggestions
Consolidate the three separate warning/authority callout blocks (prerequisite check, validation authority, mandatory next step) into the steps table or a single concise constraints section to reduce token overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the prerequisite check callout, the validation authority callout, and the mandatory next step callout all repeat information that's already in the steps table. The multiple bold/emoji warning blocks add visual noise and token cost. | 2 / 3 |
Actionability | Provides concrete, executable validation commands (azd provision --preview, bicep build, bicep lint, terraform fmt/validate, npm run scripts), specific file paths to read/write, and clear instructions for recording proof and updating status. The steps table gives precise actions with references. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit validation checkpoints: run validation, build verification, record proof, resolve errors before proceeding, and only set status to Validated after all checks pass. The feedback loop (fix failures → re-run) is explicitly stated in both the steps and the APEX-specific references section. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, a reference index table with 'when to load' guidance, explicit instruction to load on demand rather than all at once, and one-level-deep references to recipe READMEs, error docs, and policy/region references. Navigation is well-signaled. | 3 / 3 |
Total | 11 / 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
05d7617
- 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.