Kubernetes debug
š£ Hand-rolled AI Skills distilled from my everyday experience. Git & Mise (...and others).
npx -y skills add sherifabdlnaby/skills --skill kubernetes-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use for Kubernetes Debugging Sessions
The file declares its own license as MIT. That is the authorās claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.0 KB, as published. Nobody here has run it
kubernetes-debug
Route first: the debugging procedure lives in a references/ file. Open the matching one before investigating; reading it late means redoing the diagnosis.
Router
Debugging / investigating (why is X Pending / CrashLooping / not ready / reverted / 503ing / not scaling / not provisioning) -> references/debugging.md
Guidelines
- Kubernetes is not synchronous system; it is a set of controllers, each reconciling its own desired state, it's common for controllers to not be aware the others exist even if they depend on it. Never read one controller's local complaint as the system's verdict, judge a converging system by a single frame, or trust a single source of evidence (events, especially).
- Use
evictinstead of Pod Deletion for restarts.