deployment-guide
Skill74 starsChanged 9 months agoMITView on GitHub
Guide azd-based deployments, including where azure.yaml and azd hook scripts live, the current deployment flow, troubleshooting docs, and regional/model availability checks for Azure OpenAI
- Reads credentials
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 8
Use this skill to orient users to the azd deployment setup, the hook flow, and how to validate regional/model availability.
- Distinctive: line 46
Use these Azure CLI commands to validate region/model availability:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deployment Guide Skill
Use this skill to orient users to the azd deployment setup, the hook flow, and how to validate regional/model availability.
Key Files & Locations
azure.yaml— azd config, services, and hooks (preprovision/postprovision/postdown)devops/scripts/azd/preprovision.sh— preflight checks, remote state setup, tfvars/provider configdevops/scripts/azd/postprovision.sh— post-provision tasks (App Config, local env, etc.)devops/scripts/azd/postdown.sh— post-azd downcleanup (optional state delete + purge reminder)devops/scripts/azd/helpers/preflight-checks.sh— region + quota checksinfra/terraform/— Terraform modules + paramsinfra/terraform/params/main.tfvars.*.json— environment-specific TF vars (including model_deployments)
Logical Flow (azd)
azd uppreprovisionhook:- Runs preflight checks (tools/auth/providers/region/quota)
- Resolves
AZURE_LOCATION - Configures Terraform backend (remote state or local)
- Generates
main.tfvars.jsonand provider config
- Terraform apply (infra create)
postprovisionhook:- App Config updates
- Local
.env.localgeneration - Data provisioning / phone config (interactive)
azd deploy(service build/push/deploy perazure.yaml)azd down→postdownhook (optional remote state cleanup + purge reminder)
Troubleshooting & Docs
Direct users to:
docs/getting-started/quickstart.md— first-timeazd updocs/deployment/README.md— advanced deployment and flagsdocs/operations/troubleshooting.mdandTROUBLESHOOTING.md— common errorsdocs/getting-started/README.md— region availability matrix
Regional Availability & Model Checks
Use these Azure CLI commands to validate region/model availability:
# List regions
az account list-locations -o table
# Check Azure OpenAI service availability in a region
az cognitiveservices account list-skus --kind OpenAI --location <region> -o table
# Check Cognitive Services availability (Speech, etc.)
az cognitiveservices account list-skus --kind SpeechServices --location <region> -o table
# Check OpenAI quota usage for a region (requires jq)
az cognitiveservices usage list -l <region> -o json \
| jq -r '.[] | select(.name.value | startswith("OpenAI.")) | "\(.name.value)\t\(.currentValue)/\(.limit)"'
# List deployments in a specific Azure OpenAI resource
az cognitiveservices account deployment list -g <resource-group> -n <openai-account> -o tableAlso point to devops/scripts/azd/helpers/preflight-checks.sh for the exact checks used by azd.
Custom Model Deployment Overrides
There are two layers to adjust:
- Provisioning (what gets created): edit
model_deploymentsin:infra/terraform/params/main.tfvars.*.json(env-specific)- or
infra/terraform/terraform.tfvars.example(reference)
- Runtime selection (what the app uses): set the deployment name:
AZURE_OPENAI_CHAT_DEPLOYMENT_ID(preferred for app runtime)- App Config key:
azure/openai/deployment-id
Example:
azd env set AZURE_OPENAI_CHAT_DEPLOYMENT_ID "<your-deployment-name>"
azd deployFor agent-specific overrides, update deployment_id in:
apps/artagent/backend/registries/agentstore/*/agent.yaml.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- sabahattink/antigravity-fullstack-hq★ 30same name
- thensls/nsls-builder-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- add-componentSkill
- add-endpointSkill
- add-evaluationSkill
- add-mcp-serverSkill
- add-message-handlerSkill
- add-toolSkill
- add-voice-handlerSkill
- create-agentSkill
- observability-insightsSkill
- service-catalogSkill
- test-and-documentSkill
- troubleshootSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

