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

azure-deploy

Skill11 starsChanged 9 months agoMITView on GitHub

Execute Azure deployments after preparation and validation are complete. USE FOR: azd up, azd deploy, push to Azure, publish to Azure, ship to production, launch on Azure, go live, release to Azure, deploy web app, deploy container app, deploy static site, deploy Azure Functions, azd provision, infrastructure deployment, bicep deploy, terraform apply. DO NOT USE FOR: preparing new apps (use azure-prepare), validating before deploy (use azure-validate).

7 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 1 is common, 0 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run azd up or az deployment

    line 18
  2. Common:

    Run after azure-prepare and azure-validate

    line 24

“Common” is measured: kept by at least 6 in 10 of the 6 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 Deploy

AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE

PREREQUISITE: The azure-validate skill MUST be invoked and completed with status Validated BEFORE executing this skill.

Triggers

Activate this skill when user wants to:

  • Deploy their application to Azure
  • Publish, host, or launch their app
  • Push updates to existing deployment
  • Run azd up or az deployment
  • Ship code to production
  • Deploy Azure Functions to the cloud

Rules

  1. Run after azure-prepare and azure-validate
  2. Manifest must exist with status Validated
  3. Pre-deploy checklist required — pre-deploy-checklist
  4. ⛔ Destructive actions require ask_user — global-rules

Steps

#ActionReference
1Check Manifest — Verify status = Validated—
2Pre-Deploy Checklist — MUST complete ALL stepspre-deploy-checklist
3Load Recipe — Based on recipe.type in manifestrecipes/
4Execute Deploy — Follow recipe stepsRecipe README
5Handle Errors — See recipe's errors.md—
6Verify Success — Confirm deployment completed and endpoints are accessible—

Recipes

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

MCP Tools

ToolPurpose
mcp_azure_mcp_subscription_listList available subscriptions
mcp_azure_mcp_group_listList resource groups in subscription
mcp_azure_mcp_azdExecute AZD commands

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