Drin K8s Pod Troubleshooter
Systematic diagnostic workflow for failing Kubernetes pods (CrashLoopBackOff, Pending, etc).
Install
$ agentstack add skill-pedrol-cmd-brain-drin-drin-k8s-pod-troubleshooter ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
K8s Pod Troubleshooter
Purpose
To minimize downtime by rapidly identifying and fixing container orchestration issues.
Diagnostic Steps
- Status Check:
kubectl get pods- identify the failure state. - Describe:
kubectl describe pod [name]- check events and resource limits. - Logs:
kubectl logs [name] --previous- see why the container crashed. - Shell: If pod is running,
kubectl execto check environment and connectivity. - Fix: Update deployment manifest or configmaps based on findings.
Output
A ROOT-CAUSE-REPORT.md with the fix applied and prevention steps.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: pedrol-cmd
- Source: pedrol-cmd/brain-drin
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.