Azure/AKS-Skills is a collection of agent skills for operating Azure Kubernetes Service clusters after they are provisioned. It helps compatible coding agents investigate incidents, control costs, assess AKS Automatic readiness, run GPU and inference workloads, capture packet-level evidence, and design clusters. The catalogue entries provide the skills, MCP integration, and plugin configuration for these AKS operations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Azure/AKS-Skills --skill aks-troubleshootinggit clone --depth 1 https://github.com/Azure/AKS-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/azure/aks-skills/aks-troubleshooting)<a href="https://agentmods.dev/skills/azure/aks-skills/aks-troubleshooting"><img src="https://agentmods.dev/badge/skills/azure/aks-skills/aks-troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/azure/aks-skills/aks-troubleshooting"><img src="https://agentmods.dev/badge/skills/azure/aks-skills/aks-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00203 | $0.02118 |
| Opus 5 | $0.00102 | $0.01059 |
| Sonnet 5 | $0.00041 | $0.00424 |
| Haiku 4.5 | $0.00020 | $0.00212 |
Grade A, and why
aks-troubleshooting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AKS Troubleshooting
Root-cause live AKS incidents with a read-only, evidence-first investigation. This skill covers the full Day-2 troubleshooting surface — workloads, nodes, networking, ingress, upgrades, and spot/zone disruptions — and produces a structured incident report.
Operating rules
Read-only by default. Do not restart, delete, cordon, drain, scale, upgrade, or reconfigure any resource unless the user explicitly asks for remediation. Gather evidence, name the root cause, and propose the fix — but do not apply it uninvited.
Evidence before conclusion. Do not state a root cause without quoting the evidence that supports it. "Pod is Pending" and "node is NotReady" are symptoms, not causes — trace them to the specific selector, taint, exhausted resource, or Azure-side condition.
Tool preference. Inspect the host's available tools for Azure MCP capabilities that advertise AKS, AppLens, Azure Monitor, or Resource Health operations. Use each matching capability under its host-assigned name, preferring the smallest operation that fits the read. Never treat a specific prefix or spelling as an availability check, and do not invent a name-mapping layer. Fall back to raw az aks and kubectl only when the host exposes no matching capability or the discovered MCP surface cannot perform the check. Default the MCP access mode to readonly. See references/aks-mcp.md.
Evidence order. Gather Azure-side state first (cluster state, resource health, recent operations, node-pool state, detector/monitoring output), then Kubernetes-side state (reachability, nodes, kube-system, events, the affected namespace, pod detail, logs). This ordering catches platform-level causes — a failed upgrade operation, a stopped cluster, a quota block — before you spend time inside the cluster.
Route by symptom
| Symptom | Reference |
|---|---|
| Broad investigation, unknown root cause | general-diagnostics.md |
| Pod crash, OOMKilled, ImagePullBackOff, Pending, readiness probe | pod-failures.md |
| Node NotReady, node pressure, node scaling / autoscaler not triggering | node-issues.md |
| Service connectivity, DNS, pod-to-pod networking | networking.md |
| Ingress 502/503, load-balancer health probe, external access | load-balancer-and-ingress.md |
| Network policy blocking traffic | network-policy.md |
| Upgrade stuck, cordon/drain failure | upgrade-operations.md |
| Spot eviction, zone rebalance failure | spot-and-zone-issues.md |
| Any symptom → exact commands, in order | references/symptom-map.md |
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- general-diagnostics.md 2.1 KB
- load-balancer-and-ingress.md 3.6 KB
- network-policy.md 1.2 KB
- networking.md 33 KB
- node-issues.md 6.4 KB
- pod-failures.md 7.7 KB
- references/aks-mcp.md 2.4 KB
- references/command-flows.md 3.0 KB
- references/inspektor-gadget.md 7.0 KB
- references/report-template.md 603 B
- references/structured-input-modes.md 1.5 KB
- references/symptom-map.md 13 KB
- scripts/cluster-snapshot.sh 2.1 KB runs code
- scripts/pod-deep-dive.sh 1.3 KB runs code
- spot-and-zone-issues.md 2.5 KB
- upgrade-operations.md 4.3 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 82 lines · 203 tokens per session scan A e3af604634f7
aks-troubleshooting is a skill published in the GitHub repository Azure/AKS-Skills (4 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 2,118 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
aks-mcp
Azure Kubernetes Service (AKS) official MCP server.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
competition-container-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is…
applicationinsights-web-ts
Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web). Use for Real User Monitoring (RUM) — page views, clicks, AJAX/fetch dependencies, exceptions, custom events, and browser-side GenAI agent traces correlated to backend OpenTelemetry traces. Covers SDK Loader…
azure-diagnostics
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black…
azure-prepare
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd…