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.
Install with Tessl CLI
npx tessl i github:microsoft/azure-skills --skill azure-validate88
Quality
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (configuration, infrastructure, permissions validation), uses third-person voice correctly, includes an explicit 'WHEN:' clause with comprehensive natural trigger terms, and maintains a clear Azure pre-deployment validation niche that distinguishes it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deep checks on configuration, infrastructure (Bicep or Terraform), permissions, and prerequisites' - covers distinct validation domains with specific technologies named. | 3 / 3 |
Completeness | Clearly answers both what ('Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure, permissions, and prerequisites') and when (explicit 'WHEN:' clause with comprehensive trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'validate my app', 'check deployment readiness', 'run preflight checks', 'verify configuration', 'check if ready to deploy', 'test before deploying', 'troubleshoot deployment errors' - these are exactly what users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Azure-specific focus, pre-deployment validation niche, and specific technologies (Bicep, Terraform, Azure Functions). Clear separation from general deployment or configuration 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 skill has excellent workflow structure with clear sequencing, validation gates, and proof requirements. However, it sacrifices actionability by deferring all concrete commands to external recipe files, and contains some redundant emphasis blocks that could be consolidated for better token efficiency.
Suggestions
Add at least one concrete example validation command inline (e.g., `azd provision --preview` or `bicep build main.bicep`) rather than deferring all specifics to recipes
Consolidate the three callout boxes (prerequisite check, validation authority, mandatory next step) into a single 'Critical Rules' section to reduce redundancy
| 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 information. The workflow chain is stated multiple times. | 2 / 3 |
Actionability | Steps are listed but lack concrete commands - references to 'recipe-specific validation commands' and 'See recipe' defer actual executable guidance to external files. No copy-paste ready examples of validation commands are provided. | 2 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoints, proof recording requirements, and a feedback loop (Step 5: fix failures before proceeding). The workflow includes proper gates preventing progression without validation. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, table-based steps, and one-level-deep references to recipes/README.md and global-rules.md. Content is appropriately split between this skill and referenced materials. | 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.
Table of Contents
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.