K8s Debug

When pods are stuck in CrashLoopBackOff or your deployment rollout hangs at 2am, this gives you a systematic playbook instead of panic-Googling kubectl commands. It includes three diagnostic scripts: cluster_health.sh for cluster-wide snapshots, pod_diagnostics.py for deep pod analysis with logs and events, and network_debug.sh for DNS and connectivity issues. Everything defaults to read-only until you explicitly confirm destructive actions like force-deletes or rollbacks. The workflow guides are organized by symptom, so you can jump straight to "why is my PVC pending" without reading the whole thing. It assumes you have kubectl access but gracefully degrades if optional tools like jq or metrics-server are missing.

skills.sh installs: 887
GitHub stars: 337
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add akin-ozer/cc-devops-skills --skill k8s-debug --agent claude-code

Installs into .claude/skills of the current project.

Files

Kubernetes Debugging Skill

Overview

Systematic toolkit for debugging Kubernetes clusters, workloads, networking, and storage with a deterministic, safety-first workflow.

Trigger Phrases

Use this skill when requests resemble:

"My pod is in CrashLoopBackOff; help me find the root cause."
"Service DNS works in one pod but not another."
"Deployment rollout is stuck."
"Pods are Pending and not scheduling."
"Cluster health looks degraded after a change."
"PVC is pending and pods cannot mount storage."

Prerequisites

Run from the skill directory (devops-skills-plugin/skills/k8s-debug) so relative script paths work as written.

Required

kubectl installed and configured.
An active cluster context.
Read access to namespaces, pods, events, services, and nodes.

Quick preflight:

kubectl config current-context
kubectl auth can-i get pods -A
kubectl auth can-i get events -A
kubectl get ns

Optional but Recommended

jq for more precise filtering in ./scripts/cluster_health.sh.
Metrics API (metrics-server) for kubectl top.
In-container debug tools (nslookup, getent, curl, wget, ip) for deep network tests.