How do I install the Kubernetes Debug skill?

Run npx skillmds@latest add incidentfox/kubernetes-debug-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubernetes Debug safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubernetes Debug?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubernetes Debug free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubernetes Debug?

incidentfox (@incidentfox) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubernetes Debug by incidentfox — Agent Skill

Name: Kubernetes Debug
Author: incidentfox

File contents

Kubernetes Debugging

Core Principle: Events Before Logs

ALWAYS check pod events BEFORE logs. Events explain 80% of issues faster:

OOMKilled → Memory limit exceeded
ImagePullBackOff → Image not found or auth issue
FailedScheduling → No nodes with enough resources
CrashLoopBackOff → Container crashing repeatedly

Available Scripts

All scripts are in .claude/skills/infrastructure-kubernetes/scripts/

list_pods.py - List pods with status

python .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n <namespace> [--label <selector>]

# Examples:
python .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n default
python .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n default --label app=myapp

get_events.py - Get pod events (USE FIRST!)

python .claude/skills/infrastructure-kubernetes/scripts/get_events.py <pod-name> -n <namespace>

# Example:
python .claude/skills/infrastructure-kubernetes/scripts/get_events.py my-pod-7f8b9c6d5-x2k4m -n default

get_logs.py - Get pod logs

python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py <pod-name> -n <namespace> [--tail N] [--container NAME]

# Examples:
python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py my-pod-7f8b9c6d5-x2k4m -n default --tail 100
python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py my-pod-7f8b9c6d5-x2k4m -n default --container mycontainer

describe_pod.py - Detailed pod info

python .claude/skills/infrastructure-kubernetes/scripts/describe_pod.py <pod-name> -n <namespace>

get_resources.py - Resource usage vs limits

python .claude/skills/infrastructure-kubernetes/scripts/get_resources.py <pod-name> -n <namespace>

Debugging Workflows

Pod Not Starting (Pending/CrashLoopBackOff)

list_pods.py - Check pod status
get_events.py - Look for scheduling/pull/crash events
describe_pod.py - Check conditions and container states
get_logs.py - Only if events don't explain

Pod Restarting (OOMKilled/Crashes)

get_events.py - Check for OOMKilled or error events
get_resources.py - Compare usage vs limits
get_logs.py - Check for errors before crash
describe_pod.py - Check restart count and state

Deployment Not Progressing

list_pods.py - Find stuck pods
get_events.py - Check events on stuck pods
describe_pod.py - Check conditions for clues
get_resources.py - Check if resource constraints are blocking

Common Issues & Solutions

Event Reason	Meaning	Action
OOMKilled	Container exceeded memory limit	Increase limits or fix memory leak
ImagePullBackOff	Can't pull image	Check image name, registry auth
CrashLoopBackOff	Container keeps crashing	Check logs for startup errors
FailedScheduling	No node can run pod	Check node resources, taints
Unhealthy	Liveness probe failed	Check probe config, app health

Output Format

When reporting findings, use this structure:

## Kubernetes Analysis

**Pod**: <name>
**Namespace**: <namespace>
**Status**: <phase> (Restarts: N)

### Events
- [timestamp] <reason>: <message>

### Issues Found
1. [Issue description with evidence]

### Root Cause Hypothesis
[Based on events and logs]

### Recommended Action
[Specific remediation step]

---name: kubernetes-debug-2description: Kubernetes debugging methodology and scripts. Use for pod crashes, CrashLoopBackOff, OOMKilled, deployment issues, resource problems, or container failures.---# Kubernetes Debugging## Core Principle: Events Before Logs**ALWAYS check pod events BEFORE logs.** Events explain 80% of issues faster:- OOMKilled → Memory limit exceeded- ImagePullBackOff → Image not found or auth issue- FailedScheduling → No nodes with enough resources- CrashLoopBackOff → Container crashing repeatedly## Available ScriptsAll scripts are in `.claude/skills/infrastructure-kubernetes/scripts/`### list_pods.py - List pods with status```bashpython .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n <namespace> [--label <selector>]# Examples:python .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n defaultpython .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n default --label app=myapp```### get_events.py - Get pod events (USE FIRST!)```bashpython .claude/skills/infrastructure-kubernetes/scripts/get_events.py <pod-name> -n <namespace># Example:python .claude/skills/infrastructure-kubernetes/scripts/get_events.py my-pod-7f8b9c6d5-x2k4m -n default```### get_logs.py - Get pod logs```bashpython .claude/skills/infrastructure-kubernetes/scripts/get_logs.py <pod-name> -n <namespace> [--tail N] [--container NAME]# Examples:python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py my-pod-7f8b9c6d5-x2k4m -n default --tail 100python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py my-pod-7f8b9c6d5-x2k4m -n default --container mycontainer```### describe_pod.py - Detailed pod info```bashpython .claude/skills/infrastructure-kubernetes/scripts/describe_pod.py <pod-name> -n <namespace>```### get_resources.py - Resource usage vs limits```bashpython .claude/skills/infrastructure-kubernetes/scripts/get_resources.py <pod-name> -n <namespace>```## Debugging Workflows### Pod Not Starting (Pending/CrashLoopBackOff)1. `list_pods.py` - Check pod status2. `get_events.py` - Look for scheduling/pull/crash events3. `describe_pod.py` - Check conditions and container states4. `get_logs.py` - Only if events don't explain### Pod Restarting (OOMKilled/Crashes)1. `get_events.py` - Check for OOMKilled or error events2. `get_resources.py` - Compare usage vs limits3. `get_logs.py` - Check for errors before crash4. `describe_pod.py` - Check restart count and state### Deployment Not Progressing1. `list_pods.py` - Find stuck pods2. `get_events.py` - Check events on stuck pods3. `describe_pod.py` - Check conditions for clues4. `get_resources.py` - Check if resource constraints are blocking## Common Issues & Solutions| Event Reason | Meaning | Action ||--------------|---------|--------|| OOMKilled | Container exceeded memory limit | Increase limits or fix memory leak || ImagePullBackOff | Can't pull image | Check image name, registry auth || CrashLoopBackOff | Container keeps crashing | Check logs for startup errors || FailedScheduling | No node can run pod | Check node resources, taints || Unhealthy | Liveness probe failed | Check probe config, app health |## Output FormatWhen reporting findings, use this structure:```## Kubernetes Analysis**Pod**: <name>**Namespace**: <namespace>**Status**: <phase> (Restarts: N)### Events- [timestamp] <reason>: <message>### Issues Found1. [Issue description with evidence]### Root Cause Hypothesis[Based on events and logs]### Recommended Action[Specific remediation step]```

Frequently asked questions

Kubernetes Debug