CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly scoped orchestration skill: it delegates step detail to a workflow script while giving concrete commands, a hard prerequisite gate, explicit validation checkpoints, and safe hand-off rules for deployment. The only weaknesses are mild redundancy in the emphasis blocks and a recipes hub that pushes most reference content two levels deep.

Suggestions

State the azure-prepare → azure-validate → azure-deploy ordering once (e.g., in the STOP prerequisite block) and drop the repetition in Rule 1 and the closing block.

Add one-line links from the body to the top-level reference docs (region-availability.md, policy-validation.md, aspire-functions-secrets.md) or note that the recipes README indexes them, so they are discoverable without traversing the per-tool recipe folders.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ('Run the workflow script and follow its instructions'), but the azure-prepare → azure-validate ordering is stated three times (workflow chain diagram, STOP block, Rule 1) and the 'AUTHORITATIVE GUIDANCE' / 'VALIDATION AUTHORITY' emphasis blocks restate the same MUST constraints, so a few tokens could be trimmed. Not a 5 because not every token earns its place; not a 3 because there is no over-explanation of concepts Claude already knows.

4 / 5

Actionability

Gives copy-paste-ready commands for both platforms ('pwsh references/scripts/workflow.ps1 -WorkspacePath <workspace-path>' and the bash equivalent) plus a concrete iteration protocol ('re-run with that value (-CompletedStep <value>) ... Repeat until it reports the azure-validate workflow is complete'), and all referenced files (workflow.ps1/.sh, recipes/README.md, role-verification.md, global-rules.md) exist in the bundle. Fully executable guidance covering the common flow.

5 / 5

Workflow Clarity

Clear sequenced flow with an explicit prerequisite gate ('azure-prepare was invoked ... status Approved or later'), script-driven checkpoints recorded in '.azure/validate-status.json', an explicit pass rule ('All checks must pass—do not deploy with failures'), and an error-recovery feedback loop ('If any validation failed, fix the issues and re-run azure-validate'), plus a destructive-action 'ask_user' guard. Meets the anchor for explicit validation steps and feedback loops.

5 / 5

Progressive Disclosure

The body is a well-signaled overview with verified one-level links (workflow scripts, recipes/README.md, role-verification.md, global-rules.md) and the bundle is coherently organized by tool. Not a 5 because the bulk of validation detail sits two levels deep via the recipes hub (SKILL.md → recipes/README.md → bicep/README.md → region-availability.md etc.) and several top-level reference docs are not surfaced from the body itself.

4 / 5

Total

18

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, explicit WHEN triggers with natural synonyms and file names, and a well-defined Azure pre-deployment niche. The only residual risk is mild overlap with sibling azure-prepare/azure-deploy skills on generic phrases like 'troubleshoot deployment errors'.

DimensionReasoningScore

Specificity

Lists multiple concrete check targets — 'configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites' plus 'what-if analysis' — with comprehensive coverage across Azure deployment domains (azure.yaml, Azure Functions, Container Apps). Not a 4 because there are no meaningful gaps in coverage; the description is in third person, so no voice penalty applies.

5 / 5

Completeness

Explicitly answers both: 'what' via 'Pre-deployment validation for Azure readiness. Run deep checks on ... before deploying', and 'when' via the explicit 'WHEN:' clause with concrete trigger phrases. Matches the anchor exactly.

5 / 5

Trigger Term Quality

The WHEN clause is an extensive list of natural user phrasings with synonyms and concrete artifacts: 'validate my app, check deployment readiness, run preflight checks, ... validate azure.yaml, validate Bicep, ... verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis'. Covers natural terms, synonyms ('validate function app' / 'validate Azure Functions'), and file names.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (Azure pre-deployment validation between azure-prepare and azure-deploy) with Azure-specific triggers like 'validate azure.yaml' and 'verify RBAC roles'. Not a 5 because broad phrases such as 'troubleshoot deployment errors', 'test before deploying', and 'verify configuration' create minor overlap risk with the closely related sibling prepare/deploy skills.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 8 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/azure-validate/SKILL.md

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.