What problem does it solve? When a Kubernetes node enters NotReady, MemoryPressure, DiskPressure, or PIDPressure, on-call engineers need a safe, read-only diagnostic procedure that gathers the right evidence without risking destructive actions like drain or cordon. ## Core Features & Use Cases - Node Condition Diagnosis: Collects node inventory JSON, describe output, resource usage, and per-node pod lists via four deterministic kubectl steps. - Pressure Analysis: Interprets Ready, MemoryPressure, DiskPressure, and PIDPressure conditions against allocatable capacity and pod resource requests. - Safe Escalation: Enforces read-only operation with explicit NEVER DO rules and structured escalation handoffs including full command outputs. - Use Case: A node shows MemoryPressure and pods keep getting evicted. Run this skill to gather node conditions, identify the highest-memory pods as eviction candidates, and escalate with complete evidence—without executing any mutating commands. ## Quick Start Ask the AI to diagnose why a Kubernetes node is in NotReady or MemoryPressure state using read-only kubectl commands.