kubernetes-health

Kubernetes cluster health checks can be automated by discovering installed operators and running targeted diagnostics across them. This Skill dynamically detects APIs in your cluster, maps them to specialized health agents, and aggregates results into a single scored health report without manual checklists.

Yes. Multi-operator clusters require health checks tailored to each installed operator. This Skill performs API discovery to identify all operators, dispatches specialized agents to each, and generates unified health assessments covering your entire operator stack.

Pre-change validation runs health diagnostics across your cluster's operators to establish a baseline. This Skill automates operator discovery and health checks, producing a scored health report you can compare against post-change state to detect regressions.

Yes. This Skill requires kubectl for cluster access, Python 3.11 or later for the diagnostic engine, and uv as the runtime manager. These dependencies enable API discovery, agent dispatch, and health report aggregation.

Cluster diagnostics are aggregated into a JSON health-report schema with weighted scores (0-100) and operator-level details. This Skill outputs stakeholder-ready reports summarizing health status across all discovered operators in your cluster.

Onboarding to unknown clusters is error-prone without visibility into installed operators. This Skill automatically discovers all APIs and operators, runs health checks against each, and produces a diagnostic report so you understand cluster composition and health immediately.