kube-medic

Diagnose Kubernetes cluster health and root causes using kubectl.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, jq, and includes scripts (resource) components.

What problem does it solve?

Kubernetes clusters often suffer from silent failures or cascading issues that are hard to diagnose quickly. kube-medic provides rapid triage by querying cluster state across nodes, pods, deployments, resources, and events to surface root causes and guide remediation.

Core Features & Use Cases

  • Full cluster triage (sweep) to surface non-running pods, readiness issues, crashes, and warning events.
  • Pod autopsy (pod) with container statuses, logs, events, and image mismatch detection.
  • Deployment analysis (deploy) including rollout status, history, and related ReplicaSets.
  • Resource and event insights (resources, events) to identify CPU/memory pressure and recent changes.
  • Multi-cluster support via context flag to switch clusters, plus read-only safety with explicit write approvals for remediation.
  • Outputs structured JSON suitable for AI consumption and integration with Control UI workflows.

Quick Start

Ask kube-medic to run a full cluster triage with sweep to identify health issues, and then inspect a specific pod with pod <name> if needed.

Frequently Asked Questions about kube-medic

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

FAQPage Schema
How do I diagnose Kubernetes cluster health issues and find root causes?

Diagnose Kubernetes cluster health by running a triage sweep to surface non-running pods, readiness issues, crashes, and warning events, then inspect specific pods or deployments to find root causes.

What is the best way to triage pods and deployments across multiple k8s clusters?

Triage pods and deployments across multi-cluster environments by using context flags to switch clusters, reporting node health, pod states, resource usage, and recent events to guide remediation workflows.

Can I safely run kubectl diagnostics without accidentally modifying my cluster state?

Yes, kubectl diagnostics default to a strict read-only mode that only queries cluster state; any write or remediation action requires explicit user approval through a designated workflow.

How do I analyze Kubernetes deployment rollout failures and related ReplicaSets?

Analyze Kubernetes deployment rollout failures by checking rollout status, deployment history, and related ReplicaSets to identify configuration issues, image mismatches, or rollout stalls.

Do I need kubectl and jq installed to run kube-medic triage workflows?

Yes, you need kubectl and jq installed, as the Skill relies on kubectl to query cluster state and jq to parse and output structured JSON data for AI consumption.

Why are my Kubernetes pods crashing and how do I perform a pod autopsy?

Perform a pod autopsy to investigate crashing Kubernetes pods by examining container statuses, logs, recent events, and image mismatch detection to surface the underlying failure cause.