Azure Prepare β azd Deployment Planner
Plan-first preparation for azd deployments β generates azure.yaml, Bicep/Terraform and Dockerfiles behind a mandatory user-approved plan
- What
- Plan-first preparation for azd deployments β generates azure.yaml, Bicep/Terraform and Dockerfiles behind a mandatory user-approved plan
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Paid Azure subscription required β Curated by Skill Harbor β Microsoft's plan-first preparation skill for Azure Developer CLI (azd) projects: it analyzes your workspace, gathers requirements, selects a recipe (AZD, AZCLI, Bicep or Terraform), then generates `azure.yaml`, infrastructure templates and Dockerfiles β but never before writing a `.azure/deployment-plan.md` skeleton and getting your explicit approval. Routes specialized stacks (Python App Service, AI gateway, cross-cloud migration) to dedicated skills first, hardens security (Entra-only SQL auth, no hardcoded credentials), and hands off to azure-validate before anything deploys. By @microsoft, listed here with credit to its creator. Honest caveats: preparation only β it generates infrastructure code but never runs deployments itself; the mandatory plan-and-approve workflow slows down quick experiments, deliberately, to prevent surprises. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Azure Prepare β azd Deployment Planner" for me. Plan-first preparation for azd deployments β generates azure.yaml, Bicep/Terraform and Dockerfiles behind a mandatory user-approved plan Repository: https://github.com/microsoft/azure-skills/blob/main/.github/plugins/azure-skills/skills/azure-prepare/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "microsoft-azure-prepare". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.