azure-diagnoselisted
Install: claude install-skill viettdann/arclight-kit
# Azure diagnose
Two modes. **Diagnose**: find out why one running workload misbehaves, from evidence with timestamps (sections 1 to 4). **Audit**: survey a tenant for what is failing, at risk, or unobservable, then rank it ([Audit](#audit)). Both are read-only: no restart, scale, setting change, redeploy, or diagnostic setting added, even when it is the obvious fix. Give the fix and the command, and let the user run it.
## Audit
When the user asks what is wrong or worth fixing across Azure rather than about one symptom:
```
python3 ${CLAUDE_SKILL_DIR}/scripts/audit.py [--tenant TENANT] [--days 7] [--rg FRAGMENT] [--no-cost]
```
It prints active Azure service issues first (an outage explains everything below it), then **BROKEN** (failing now: Resource Health `Unavailable`, crashed containers, failed job runs, dead letters, a 5xx rate of 1% or more, exhausted CPU credits, connections at `max_connections`, not-ready revisions), **RISK** (Resource Health `Degraded`, runtimes past or near end of support, in-process .NET Functions, Functions hosts older than 4.x, Key Vault secrets and keys expired or expiring within 30 days, Basic plans shared by several apps, always-on off, no health check, Linux Consumption apps, sustained CPU or memory, Container Apps warnings, restarts, low 5xx rates), **BLIND** (apps and databases with no App Insights and no diagnostic setting), the top App Insights exceptions, and **COST**: spend per subscription and resource group over the last 30 days