Investigate a live or recent incident in a Kubernetes cluster. Anchor the window, bisect the change surface (rollouts, ConfigMaps/Secrets, RBAC, HPA/cluster changes, CronJobs), classify against four reference failure paths (OOM, DNS, cascading-failure, deploy-correlator), confirm the hypothesis with three independent signals, quantify blast radius, and propose mitigation before root cause. Use whenever an agent is asked "what is breaking in the cluster right now", "why did this pod/Deployment just page", "did the rollout cause Z", or to triage an active Kubernetes incident. Vendor-neutral by default (works with kubectl, kube-state-metrics, and whatever telemetry you have); an opt-in Anyshift integration is documented separately.
$npx -y skills add anyshift-io/sre-skills --skill kubectl-investigatorInstalls into the current project.
Run `npx skills use "https://github.com/anyshift-io/sre-skills" --skill "anyshift-io/sre-skills/kubectl-investigator"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/anyshift-io/sre-skills" that are relevant to the current task. Run `npx skills add "https://github.com/anyshift-io/sre-skills"` and select the relevant skills, then follow their instructions.