azure-validate
Performs critical pre-flight checks to ensure Azure environments are ready for deployment.
Install
mkdir -p .claude/skills/azure-validate-ricardoaevt && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17743" && unzip -o skill.zip -d .claude/skills/azure-validate-ricardoaevt && rm skill.zipInstalls to .claude/skills/azure-validate-ricardoaevt
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
|Key capabilities
- →Validate infrastructure configuration for Azure deployment
- →Check permissions and prerequisites before deployment
- →Record validation proof in `.azure/plan.md`
- →Resolve errors identified during validation
- →Update the plan status to `Validated` upon success
How it works
The skill loads a deployment plan from `.azure/plan.md`, executes recipe-specific validation commands, and records the results. It updates the plan's status to `Validated` only after all checks pass.
Inputs & outputs
When to use azure-validate
- →Validating azure.yaml
- →Checking deployment readiness
- →Troubleshooting azure deployment errors
About this skill
Azure Validate
AUTHORITATIVE GUIDANCE — Follow these instructions exactly. This supersedes prior training.
⛔ STOP — PREREQUISITE CHECK REQUIRED
Before proceeding, verify this prerequisite is met:
azure-prepare was invoked and completed →
.azure/plan.mdexists with statusApprovedor laterIf the plan is missing, STOP IMMEDIATELY and invoke azure-prepare first.
The complete workflow ensures success:
azure-prepare→azure-validate→azure-deploy
Triggers
- Check if app is ready to deploy
- Validate azure.yaml or Bicep
- Run preflight checks
- Troubleshoot deployment errors
Rules
- Run after azure-prepare, before azure-deploy
- All checks must pass—do not deploy with failures
- ⛔ Destructive actions require
ask_user— global-rules
Steps
| # | Action | Reference |
|---|---|---|
| 1 | Load Plan — Read .azure/plan.md for recipe and configuration. If missing → run azure-prepare first | .azure/plan.md |
| 2 | Run Validation — Execute recipe-specific validation commands | recipes/README.md |
| 3 | Record Proof — Populate Section 7: Validation Proof with commands run and results | .azure/plan.md |
| 4 | Resolve Errors — Fix failures before proceeding | See recipe's errors.md |
| 5 | Update Status — Only after ALL checks pass, set status to Validated | .azure/plan.md |
| 6 | Deploy — Invoke azure-deploy skill | — |
⛔ VALIDATION AUTHORITY
This skill is the ONLY authorized way to set plan status to
Validated. You MUST:
- Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.)
- Populate Section 7: Validation Proof with the commands you ran and their results
- Only then set status to
ValidatedDo NOT set status to
Validatedwithout running checks and recording proof.
⚠️ MANDATORY NEXT STEP — DO NOT SKIP
After ALL validations pass, you MUST invoke azure-deploy to execute the deployment. Do NOT attempt to run
azd up,azd deploy, or any deployment commands directly. Let azure-deploy handle execution.If any validation failed, fix the issues and re-run azure-validate before proceeding.
When not to use it
- →When creating or building applications
- →When executing deployments
- →When `.azure/plan.md` is missing or not in `Approved` status
Prerequisites
Limitations
- →Requires `.azure/plan.md` to be in `Approved` status or later
- →Does not create or build applications
- →Does not execute deployments
How it compares
This skill acts as a pre-deployment checkpoint, specifically validating configurations and permissions against a pre-approved plan, rather than performing the deployment itself or initial setup.
Compared to similar skills
azure-validate side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| azure-validate (this skill) | 0 | 4mo | No flags | Intermediate |
| deployment-pipeline-design | 6 | 2mo | Review | Advanced |
| terraform-module-library | 7 | 4mo | No flags | Advanced |
| ecs | 2 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ricardoaevt
View all by ricardoaevt →You might also like
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
terraform-module-library
wshobson
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
ecs
itsmostafa
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
genkit-infra-expert
jeremylongshore
Execute use when deploying Genkit applications to production with Terraform. Trigger with phrases like "deploy genkit terraform", "provision genkit infrastructure", "firebase functions terraform", "cloud run deployment", or "genkit production infrastructure". Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows.
cloudformation
itsmostafa
AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.
enter-services
pollinations
Deploy and manage enter.pollinations.ai text/image services on EC2 and Cloudflare Workers. Requires: SSH keys, sops, wrangler.