kubernetes-health

Diagnose Kubernetes cluster health through dynamic API discovery and multi-agent report aggregation.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/brillianodhiya/VisionScript --skill kubernetes-health-brillianodhiya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubernetes-health
Source: https://github.com/brillianodhiya/VisionScript/tree/main/.agents/skills/kubernetes-health
Command: npx skills add https://github.com/brillianodhiya/VisionScript --skill kubernetes-health-brillianodhiya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubernetes, and includes scripts (resource) and references (resource) components.

What problem does it solve? Manually checking Kubernetes cluster health with static checklists misses installed operators, produces stale diagnostics, and wastes tokens on raw kubectl output. This Skill discovers every API group in the cluster, dispatches only the relevant health check agents, and aggregates results into a single scored report. ## Core Features & Use Cases - Dynamic API Discovery: Detects installed operators (Crossplane, ArgoCD, Cert-Manager, Prometheus, and more) by interrogating cluster APIs instead of relying on hardcoded checklists. - Agent Dispatch Planning: Maps discovered API groups to specialized health agents with parallel execution groups for faster multi-operator assessments. - Weighted Health Scoring: Aggregates component checks into a 0-100 score with HEALTHY, DEGRADED, or CRITICAL status and prioritized recommendations. - Use Case: When onboarding to an unfamiliar cluster, run the discovery script to see which operators are installed, dispatch the matching health agents in parallel, and generate a unified JSON or summary report for stakeholders. ## Quick Start Ask the AI to run a health assessment on the current Kubernetes cluster using the kubernetes-health skill, starting with API discovery and ending with an aggregated health report.

Frequently Asked Questions about kubernetes-health

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

FAQPage Schema
How do I check Kubernetes cluster health across multiple operators?▼

Run the discover_apis.py script to detect installed operators via API discovery, then use health_orchestrator.py to get a dispatch plan for specialized health agents. Finally, aggregate agent outputs with aggregate_report.py to produce a unified scored report.

How is a Kubernetes health score calculated for a cluster?▼

Each check is scored by status (OK=100, WARNING=70, ERROR=30) and weighted by category: availability 40%, configuration 25%, freshness 20%, resources 15%. Component scores are then weighted together, with Core at 1.0 and operators at 0.8, producing an overall 0-100 score.

Which Kubernetes operators does automated health checking support?▼

The discovery script recognizes Crossplane, ArgoCD, Cert-Manager, Prometheus, Flux, Istio, Gateway API, Karpenter, External Secrets, and Velero by their API groups. Specialized health agents exist for Core Kubernetes, Crossplane, ArgoCD, Cert-Manager, and Prometheus.

Why does Kubernetes API discovery return empty results?▼

Empty discovery results usually mean the cluster is unreachable, RBAC permissions block API group listing, or the kubectl version is incompatible. Verify connectivity with kubectl cluster-info and check permissions with kubectl auth can-i get pods --all-namespaces.

Can Kubernetes health checks modify or remediate cluster resources?▼

No, the health checks are strictly read-only and use only kubectl get, describe, and logs commands. The agents provide prioritized recommendations for identified issues, but automatic remediation is intentionally out of scope.

When should I not use a cluster-wide health assessment skill?▼

Avoid it when debugging a single pod, where direct kubectl commands are faster, or when you need real-time monitoring, since the checks are point-in-time snapshots. It also does not modify resources or perform automatic remediation.