What problem does it solve?
This Skill helps you quickly identify why a Kubernetes workload is unhealthy by organizing evidence from deployments, pods, events, and logs into a clear failure category.
Core Features & Use Cases
- Evidence-first Kubernetes incident triage: Captures cluster context, workload state, unhealthy pod details, prior logs, and recent events to ground the diagnosis.
- Failure classification for next-step guidance: Categorizes issues into image/pull, scheduling, probe, configuration, network, permission, or application crash behavior.
- Safety and production guardrails: Enforces rules that prevent destructive actions like delete without explicit confirmation and avoids production namespace modifications without override.
- Targeted escalation to specialized debug flow: If the issue appears to be application crashes or configuration, it routes toward a deeper debugging skill for actionable next steps.
Quick Start
Use the k8s-triage skill when you see kubectl or Kubernetes symptoms by asking for a triage plan for the affected namespace and workload, e.g., "Diagnose why my Kubernetes deployment is unhealthy in namespace staging and recommend the single next action."