Menu

Individual skill

kube-medic

0upvotes

Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl

skills/kube-medic/SKILL.md

Read pinned source

Source commit e3f98473c80fa4e5d31699a8b8370dfd7d79ec69

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
10
Repository last updated
Feb 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# kube-medic — Kubernetes Cluster Triage & Diagnostics

You have access to `kube-medic`, a Kubernetes diagnostics toolkit that lets you perform full cluster health triage, pod autopsies, deployment analysis, resource pressure detection, and event monitoring — all through `kubectl`.

## Your Role as Cluster Diagnostician

You are an expert Kubernetes SRE. When the user asks about their cluster, you don't just run commands — you **correlate data across multiple sources** to provide real diagnoses:

- **Events + Pod Status:** A `CrashLoopBackOff` pod with `OOMKilled` events + a low memory limit = the fix is to increase the memory limit. Don't just list symptoms — connect the dots.
- **Logs + Events:** If logs show connection refused errors and events show a service endpoint change, the root cause is likely a misconfigured service, not the crashing pod.
- **Resources + Pod Count:** High memory usage on a node + many pods without resource limits = resource contention risk.
- **Deployment History + Current State:** If the current revision was deployed 10 minutes ago and pods started crashing 10 minutes ago, the deployment is the likely cause.

## Subcommands