cluster-health

Name: cluster-health
Availability: InStock
Author: iuliandita

Run read-only Kubernetes cluster health checks and generate status reports.

2|Updated Apr 6, 2026

Search Tags:#devops #kubernetes #observability #diagnostics #kubectl #health-check

Ready to run

npx skills add https://github.com/iuliandita/skills --skill cluster-health

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cluster-health
Source: https://github.com/iuliandita/skills/tree/main/skills/cluster-health
Command: npx skills add https://github.com/iuliandita/skills --skill cluster-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a standardized, read-only diagnostic framework for Kubernetes clusters, preventing manual errors and ensuring consistent observability during incidents or maintenance.

Core Features & Use Cases

Automated Health Sweeps: Executes a comprehensive, read-only diagnostic suite covering nodes, workloads, networking, storage, and security.
Evidence-Based Reporting: Generates structured, traffic-light status reports (GREEN/YELLOW/RED) with clear evidence and actionable next steps.
Use Case: Use this skill to perform a post-maintenance check on a production cluster to verify that all pods are running, ingress is healthy, and no critical events are firing.

Quick Start

Run the cluster-health skill for the production context with a one hour time window.

Frequently Asked Questions about cluster-health

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

FAQPage Schema

How do I run a Kubernetes health check after cluster maintenance?▼

You can run a Kubernetes health check by executing a read-only diagnostic sweep across nodes, workloads, and networking. This generates a traffic-light status report verifying pod health and ingress status without modifying cluster state.

What is read-only Kubernetes diagnostics for incident response?▼

Read-only Kubernetes diagnostics for incident response is a standardized method to gather evidence across nodes, namespaces, and GitOps controllers. It ensures consistent observability without risking further infrastructure modifications during an active incident.

Do I need kubectl and helm to perform cluster health checks?▼

Yes, you need kubectl and helm access to perform these cluster health checks. These tools are required to gather the necessary diagnostic evidence across your Kubernetes infrastructure, workloads, and GitOps controllers.

Can I use automated health sweeps for routine cluster observability?▼

Yes, you can use automated health sweeps for routine cluster observability. They execute a comprehensive diagnostic suite covering storage, security, and networking, producing structured traffic-light reports with actionable next steps.

What is the best way to diagnose Kubernetes workload issues without causing changes?▼

The best way to diagnose Kubernetes workload issues safely is using a standardized read-only framework. This approach inspects workloads, nodes, and events to identify problems while ensuring no infrastructure modifications occur.