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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The body is a well-structured orchestration skill: clear sequenced workflow with validation feedback loops and clean one-level references to real bundle files. It is held back only by some redundant emphatic callouts and executable detail that is largely delegated to recipe files.

Suggestions

Collapse the 'VALIDATION AUTHORITY' and 'MANDATORY NEXT STEP' callouts into the existing Steps table (or inline one-line reminders) to remove restating of steps 6, 8, and 9.

Replace vague steps like 'Build the project and fix any errors' and 'See recipe' with the specific build command and a direct link to the relevant recipe errors.md.

Inline the 1-2 most common validation commands (e.g. `azd provision --preview`, `bicep build`, `terraform validate`) directly in step 3 rather than only naming them in the authority block.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept explanations Claude already knows, but the 'VALIDATION AUTHORITY' block restates steps 6/8 and the 'MANDATORY NEXT STEP' block restates step 9, adding emphasis padding. Not a 3 because of this genuine redundancy; not a 1 because the body is otherwise lean.	2 / 3
Actionability	Concrete file paths, statuses, and named commands ('azd provision --preview, bicep build, terraform validate') appear, but most executable detail is deferred to recipes and some steps are vague ('Build the project and fix any errors', 'See recipe'). Not a 3 because guidance is not consistently copy-paste ready; not a 1 because key actions are specific.	2 / 3
Workflow Clarity	A 9-step sequenced table with a prerequisite gate, explicit validation checkpoints, and a feedback loop ('If any validation failed, fix the issues and re-run azure-validate') for a destructive deployment operation. Not a 2 because checkpoints and error-recovery are explicit.	3 / 3
Progressive Disclosure	Clear overview body with well-signaled one-level-deep references (global-rules.md, recipes/README.md, role-verification.md) that resolve to real bundle files, with detailed validation commands split into recipe subfolders. Not a 2 because navigation is explicit and references are single-level.	3 / 3
	Total	10 / 12 Passed

Description

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.

The description is strong across the board: third-person voice, specific multi-action capability statement, an explicit WHEN trigger clause, and a distinctive Azure validation niche. No reductions apply.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites' — matching the level-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Pre-deployment validation for Azure readiness...') and when via a 'WHEN:' clause with concrete triggers, matching the level-3 anchor; not a 2 because the when guidance is explicit rather than implied.	3 / 3
Trigger Term Quality	Broad coverage of natural phrasings users would say ('validate my app', 'check deployment readiness', 'run preflight checks', 'validate Bicep', 'troubleshoot deployment errors'); not merely a 2 because it spans many common variations rather than a single keyword set.	3 / 3
Distinctiveness Conflict Risk	A clear Azure pre-deployment niche with distinct triggers (azure.yaml, Bicep, RBAC, what-if analysis) unlikely to fire for unrelated skills; not a 2 because the Azure-specific scope sharply reduces overlap.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 2 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: microsoft/azure-skills
Commit: 2cd48ca

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.