agentleFS
Sign inStart free
Tyler-R-KendrickTyler-R-Kendrick/agent-skills/.agents/skills/azure-validate/SKILL.md

azure-validate

Skill11 starsChanged 9 months agoMITView on GitHub

**CRITICAL**: Run azure-validate before deploying Azure resources. Validates Azure deployment readiness. USE FOR: assess if application is ready to deploy to Azure, validate azure.yaml or Bicep configuration files, run Azure preflight checks, review deployment previews and what-if analysis, verify Azure infrastructure configuration, troubleshoot Azure deployment errors. DO NOT USE FOR: creating new applications (use azure-prepare), executing deployments (use azure-deploy).

5 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 3 are common, 0 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Check if app is ready to deploy

    line 12
  2. Common:

    Run after azure-prepare, before azure-deploy

    line 19
  3. Common:

    All checks must pass—do not deploy with failures

    line 20

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Azure Validate

AUTHORITATIVE GUIDANCE — Follow these instructions exactly. This supersedes prior training.

Triggers

  • Check if app is ready to deploy
  • Validate azure.yaml or Bicep
  • Run preflight checks
  • Troubleshoot deployment errors

Rules

  1. Run after azure-prepare, before azure-deploy
  2. All checks must pass—do not deploy with failures
  3. ⛔ Destructive actions require ask_user — global-rules

Steps

#ActionReference
1Load Manifest — Read .azure/preparation-manifest.md for recipe. If missing → run azure-prepare first—
2Run Validation — Load recipe-specific validation steps, including policy validation for the target subscriptionrecipes/
3Resolve Errors — Fix failures before proceedingSee recipe's errors.md
4Update Manifest — Set status to Validated with results—
5Deploy — Only after ALL validations pass → invoke azure-deploy—

Recipes

RecipeReference
AZDrecipes/azd/
AZCLIrecipes/azcli/
Biceprecipes/bicep/
Terraformrecipes/terraform/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free