kube-medic

Automate Kubernetes cluster diagnostics and incident triage via kubectl commands.

3.1k|368|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/openocta/openocta --skill kube-medic-openocta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kube-medic
Source: https://github.com/openocta/openocta/tree/main/src/embed/skills/kube-medic
Command: npx skills add https://github.com/openocta/openocta --skill kube-medic-openocta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides immediate, AI-powered diagnostics for Kubernetes clusters, transforming complex kubectl commands into actionable insights for incident response and SRE tasks.

Core Features & Use Cases

  • Full Cluster Sweep: Get a comprehensive health overview including nodes, problematic pods, events, and component status with a single command.
  • Pod Autopsy: Deep-dive into failing pods, analyzing logs, events, and container states to pinpoint root causes.
  • Deployment Analysis: Track rollout status, revision history, and associated events to diagnose deployment failures.
  • Resource Monitoring: Identify CPU/memory pressure on nodes and pods, and detect pods missing resource limits.
  • Event Timeline: Review recent cluster events to understand recent changes and their impact.
  • Write Operations: Safely perform approved write actions like rollbacks, scaling, and pod deletion with explicit user confirmation.

Quick Start

Use the kube-medic skill to run a full sweep of your Kubernetes cluster.

Frequently Asked Questions about kube-medic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Kubernetes cluster diagnostics for rapid incident triage?

Automating Kubernetes cluster diagnostics involves running a full sweep of nodes, problematic pods, events, and component status to provide a comprehensive health overview for incident triage. This process uses structured JSON output to deliver actionable insights for identifying root causes.

What is the best way to perform a pod autopsy on failing Kubernetes pods?

Performing a pod autopsy requires deep-diving into failing pods by analyzing container logs, events, and container states. This isolates the exact root cause of pod failures by examining the collected diagnostic data to pinpoint underlying issues.

Can I check Kubernetes deployment rollout status and revision history during an incident?

Checking Kubernetes deployment rollout status and revision history tracks ongoing rollouts and associated events. This deployment analysis diagnoses deployment failures by reviewing rollout status and revision history to understand recent cluster changes.

Does Kubernetes incident response require read-only access by default?

Kubernetes incident response requires read-only access by default to ensure cluster safety during diagnostics. Explicit user confirmation is required before executing any approved write actions, such as rollbacks, scaling, or pod deletion.

Why are my Kubernetes pods failing and how do I identify CPU or memory pressure on nodes?

Kubernetes pods failing due to resource constraints can be identified by monitoring CPU and memory pressure on nodes. Resource monitoring detects nodes under pressure and identifies pods missing resource limits to prevent future failures.