agentleFS
creanlabcreanlab/agent-genome-lab/.agents/skills/kubernetes-pod-debugging/SKILL.md

Kubernetes Pod Debugging

Skill2 starsChanged 4 months agoMITView on GitHub

Methodology for identifying and fixing CrashLoopBackOff and OOMKilled in K8s.

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
  1. Very specific:

    When operating in the devops domain.

    line 13
  2. Distinctive:

    When resolving incidents related to kubernetes pod debugging.

    line 14
  3. Distinctive:

    If the issue requires manual human intervention.

    line 17
  4. Distinctive:

    If the domain does not apply.

    line 18
  5. Very specific:

    Check pod status with kubectl get pods and identify the failing pod.

    line 29
  6. Very specific:

    Check pod events using kubectl describe pod <pod-name> to look for OOMKilled or readiness probe failures.

    line 35
  7. Distinctive:

    If OOMKilled, review resource limits in the deployment manifest and suggest an increase based on current usage estimates.

    line 38
  8. Distinctive:

    Always verify changes in a staging environment before applying to production.

    line 48
  9. Distinctive:

    Do not execute destructive commands without explicit authorization.

    line 49

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Kubernetes Pod Debugging

Methodology for identifying and fixing CrashLoopBackOff and OOMKilled in K8s.

When to use

  • When operating in the devops domain.
  • 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.