azure-cli

**Quick judgment** A strong, Azure-CLI-centric skill that exposes broad Azure resource management via `az` commands, with good documentation and scripting patterns. It is powerful and flexible, but also potentially destructive and costly if used against production subscriptions without guardrails. **Key strengths** - Wide coverage of common Azure services (VMs, storage, AKS, monitoring, etc.) via native CLI modules. - Clear, example-driven documentation (installation, login flows, core commands, JMESPath queries, automation patterns). - Helper scripts targeting real operational needs (status checks, cleanup, storage analysis, subscription info, deployments). - Good alignment with official Azure CLI docs and practices. **Risks and limitations** - **Destructive operations**: Many examples and patterns include deletes (VMs, resource groups, cleanup scripts). Misuse can lead to data loss or service disruption. - **Cost risk**: Creating VMs, AKS clusters, and other resources can incur significant cloud costs if not carefully scoped and cleaned up. - **Security/auth risk**: Use of service principals, access tokens, and managed identities requires correct secret handling; misconfiguration could expose credentials or over-privileged identities. - **External dependency**: Depends on Azure CLI (`az`) and a valid Azure subscription; reliability is tied to Azure service availability and CLI version changes. **Best-fit scenarios** - DevOps and SRE teams managing Azure infrastructure primarily via CLI or CI/CD pipelines. - Power users or platform engineers who need scripted, repeatable control over subscriptions, resource groups, and workloads. - Automation agents that should interface with Azure via `az` rather than language-specific SDKs. - Training or lab environments where users are learning Azure CLI and need clear patterns and references, ideally on non-production subscriptions.