skillhash

Is aks-troubleshooting safe?

Grade A, 100/100. No meaningful risk found.

Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or InsufficientVCPUQuota, upgrade stuck, spot or zone disruption, a bare VMExtensionProvisioningError or AllocationFailed wrapper, an uncataloged capacity symptom, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues (use aks-gpu-inference); cluster creation or provisioning (use azure-kubernetes); cost (use cost-analysis from the optional azure-cost plugin); pod rightsizing (use azure-kubernetes); a fully qualified documented AKS signature with every required nested qualifier (use aks-known-issues); standalone failures on non-AKS Azure resources (use azure-diagnostics). Unqualified errors and open-ended incidents stay here only for AKS.

A

aks-troubleshooting

.github/plugins/aks-skills/skills/aks-troubleshooting
100/100 · No meaningful risk foundNo security findings

Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or InsufficientVCPUQuota, upgrade stuck, spot or zone disruption, a bare VMExtensionProvisioningError or AllocationFailed wrapper, an uncataloged capacity symptom, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues (use aks-gpu-inference); cluster creation or provisioning (use azure-kubernetes); cost (use cost-analysis from the optional azure-cost plugin); pod rightsizing (use azure-kubernetes); a fully qualified documented AKS signature with every required nested qualifier (use aks-known-issues); standalone failures on non-AKS Azure resources (use azure-diagnostics). Unqualified errors and open-ended incidents stay here only for AKS.

Content hash
sha256:74974610006ff820531f3f7d4bedaffe4c20713a705f7bb789f576934965a07a
Files
20
Quality
100/100

Security findings

None of the 30 rules matched.

Files in this skill
  • SKILL.md12.5 KB
  • general-diagnostics.md2.8 KB
  • load-balancer-and-ingress.md7.5 KB
  • network-policy.md1.2 KB
  • networking.md14.0 KB
  • node-issues.md15.5 KB
  • pod-failures.md8.0 KB
  • spot-and-zone-issues.md2.5 KB
  • upgrade-operations.md4.5 KB
  • references/api-server-webhooks-tunnel.md6.3 KB
  • references/auto-upgrade-evidence.md4.4 KB
  • references/azure-mcp.md2.5 KB
  • references/azure-network-path.md7.6 KB
  • references/command-flows.md3.3 KB
  • references/inspektor-gadget.md8.1 KB
  • references/report-template.md1.1 KB
  • references/structured-input-modes.md3.8 KB
  • references/symptom-map.md14.8 KB
  • scripts/cluster-snapshot.sh3.8 KB
  • scripts/pod-deep-dive.sh3.6 KB

Questions about aks-troubleshooting

Is aks-troubleshooting safe to install?
Our scanner gave aks-troubleshooting grade A (100/100): no meaningful risk found. None of the 30 security rules matched. Static analysis cannot prove safety, so pin the reviewed revision with a lockfile.
How do I install aks-troubleshooting in Claude Code or Codex?
Run skillhash add github:microsoft/azure-skills/.github/plugins/aks-skills/skills/aks-troubleshooting. It downloads the exact commit, checks the grade against your policy, writes skills.lock and installs it into .claude/skills and .agents/skills.
What happens if aks-troubleshooting changes upstream?
Its content hash changes. skillhash verify fails in CI until you review the new version and update the lock. With a watch, you also get an alert.

More from microsoft/azure-skills