Kubernetes Pod Debugging
Skill2 starsChanged 4 months agoMITView on GitHub
Methodology for identifying and fixing CrashLoopBackOff and OOMKilled in K8s.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Academic Paper SummarizationSkill
- Accessibility WCAG AuditSkill
- API Error TroubleshootingSkill
- CI/CD Pipeline TroubleshootingSkill
- Competitor Analysis SynthesisSkill
- Customer Onboarding AssistanceSkill
- Dependency Audit ResolutionSkill
- Docker Image OptimizationSkill
- GDPR Data MappingSkill
- genome-analyzerSkill
- incident-distillerSkill
- nve-genome-explorerSkill
- OWASP Input ValidationSkill
- repo-auditorSkill
- research-packagerSkill
- rule-patcherSkill
- Secret Leak RemediationSkill
- skill-curatorSkill
- skill-package-builderSkill
- SOC2 Policy VerificationSkill
- tama-community-summarizerSkill
- Technology Stack EvaluationSkill
- Ticket Triage and RoutingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
When operating in the devops domain.
- Distinctive: line 14
When resolving incidents related to kubernetes pod debugging.
- Distinctive: line 17
If the issue requires manual human intervention.
- Distinctive: line 18
If the domain does not apply.
- Very specific: line 29
Check pod status with kubectl get pods and identify the failing pod.
- Very specific: line 35
Check pod events using kubectl describe pod <pod-name> to look for OOMKilled or readiness probe failures.
- Distinctive: line 38
If OOMKilled, review resource limits in the deployment manifest and suggest an increase based on current usage estimates.
- Distinctive: line 48
Always verify changes in a staging environment before applying to production.
- Distinctive: line 49
Do not execute destructive commands without explicit authorization.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kubernetes Pod Debugging
Methodology for identifying and fixing CrashLoopBackOff and OOMKilled in K8s.
When to use
- When operating in the
devopsdomain. - When resolving incidents related to kubernetes pod debugging.
When not to use
- If the issue requires manual human intervention.
- If the domain does not apply.
Triggers
- Pattern:
kubernetes-pod-debugging - Keywords: devops, kubernetes
Inputs
- Context from the current user session or incident report.
Steps
1. Step 1
Check pod status with kubectl get pods and identify the failing pod.
2. Step 2
Inspect previous logs with kubectl logs <pod-name> --previous to find the panic or exception.
3. Step 3
Check pod events using kubectl describe pod <pod-name> to look for OOMKilled or readiness probe failures.
4. Step 4
If OOMKilled, review resource limits in the deployment manifest and suggest an increase based on current usage estimates.
Success signals
- The task is resolved without regressions.
- Logs confirm the procedure was successfully applied.
Failure modes
- Incorrect application of the steps leading to side effects.
Safety notes
- Always verify changes in a staging environment before applying to production.
- Do not execute destructive commands without explicit authorization.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

