Agent skill · software engineering · github
azure-developer-cli
Design, create, review, migrate, or troubleshoot Azure Developer CLI (azd) projects using current Microsoft guidance. Use for azd, azure.yaml, AZD templates, Bicep or Terraform under infra, AZD environments and secrets, hooks, deployment workflows, and azd-managed CI/CD.
Why this skill is useful
Provides specific guidance on Azure Developer CLI project structure, security practices, and deployment workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires azure-cli installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Azure Developer CLI best practices Use this skill to produce maintainable, secure, environment-aware azd projects. Prefer repository conventions when they are already coherent, and make the smallest complete change that improves the project. Start with repository discovery Before editing: 1. Find azure.yaml, the configured infra.path, source projects, deployment scripts, .gitignore, and pipeline definitions. 2. Read azure.yaml before inferring services or the IaC provider. 3. Identify whether the task is to create, migrate, review, deploy, or troubleshoot. 4. Identify the active environment only when an environment-specific operation is required. 5. Read the relevant reference: Repository layout or azure.yaml: references/project-structure.md Bicep, Terraform, parameters, outputs, or environments: references/iac-and-environments.md Secrets, hooks, CI/CD, deployment, or troubleshooting: references/security-cicd-operations.md Product details that may have changed: references/official-docs.md Do not assume the default infra path, the default Bicep provider, or a single service when azure.yaml says otherwise. Apply safety guardrails Never commit .azure, environment .env files, credentials, deployment outputs containing secrets, local Terraform state, or generated deployment artifacts. Never put literal secrets in azure.yaml, IaC parameter files, hooks, source control, command arguments that will be logged, or IaC outputs. Prefer managed identities and RBAC. Use Key Vault references and azd env set-secret when a secret is unavoidable. Before a command that can create, modify, or delete Azure resources, confirm the target environment, subscription, tenant, region, and expected scope. Treat an explicit user request to deploy, provision, destroy, or configure a pipeline as approval for that named action. Otherwise, ask before running azd up, azd provision, azd deploy, azd down, or azd pipeline config. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/azure-developer-cli