CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

85%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

Well-structured orchestration content: clear sequenced workflow with validation checkpoints and feedback loops, plus clean progressive disclosure to recipe references. It loses points on conciseness (redundant reinforcement blockquotes) and actionability (executable commands deferred to recipe files rather than given inline).

Suggestions

Collapse the 'VALIDATION AUTHORITY' and 'MANDATORY NEXT STEP' blockquotes into the steps table or a single short note — they restate steps 6, 8, and 9 verbatim.

Inline the key validation commands per recipe (e.g. `azd provision --preview`, `bicep build`, `terraform validate`) directly in step 3 instead of 'See recipe', so the skill is copy-paste-ready without a hop.

Add one concrete example of a populated Section 7 'Validation Proof' entry so the record-proof step is unambiguous.

DimensionReasoningScore

Conciseness

Mostly lean (compact step table, terse rules, no concept over-explanation), but the 'VALIDATION AUTHORITY' and 'MANDATORY NEXT STEP' blockquotes restate guidance already in the steps table — material that could be tightened.

2 / 3

Actionability

Gives concrete file paths and section numbers and names real commands ('azd provision --preview, bicep build, terraform validate'), but several steps defer executable detail to 'See recipe' / 'See recipe's errors.md' rather than providing copy-paste-ready commands inline.

2 / 3

Workflow Clarity

Clear 9-step numbered sequence with explicit validation checkpoints ('Only after ALL checks pass, set status to Validated'), a prerequisite STOP gate, and feedback loops ('fix failures and re-run azure-validate before proceeding').

3 / 3

Progressive Disclosure

A concise overview body with well-signaled references ([recipes/README.md], [role-verification.md], [global-rules.md]); the recipe index is a clean one-level table rather than a content-hiding chain, so navigation is easy.

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.

A strong description: third-person, specific, with an explicit WHEN clause packed with natural triggers and a clearly delineated Azure validation niche. Its only weakness is verbosity — the trigger list is long and partially redundant — but every phrase is concrete rather than fluffy, so no dimension is capped.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying' — naming specific domains rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Pre-deployment validation for Azure readiness' plus the deep-check actions) and when via an explicit 'WHEN:' trigger clause, satisfying the anchor for both.

3 / 3

Trigger Term Quality

The WHEN clause covers many natural phrases a user would say — 'validate my app', 'check deployment readiness', 'run preflight checks', 'validate azure.yaml', 'troubleshoot deployment errors', 'what-if analysis' — with strong coverage and common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Azure pre-deployment validation niche with distinct readiness/preflight triggers, unlikely to fire for the sister azure-prepare or azure-deploy skills.

3 / 3

Total

12

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.