neb-cluster-health

Identify and report health and sync issues across ArgoCD-managed Kubernetes clusters.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-cluster-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neb-cluster-health
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-cluster-health
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-cluster-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cluster health and ArgoCD state drift can lead to outages and misconfigurations; this skill identifies and reports issues across Kubernetes clusters managed by ArgoCD to help operators maintain reliability and compliance.

Core Features & Use Cases

  • Known flaky apps detection against an operational knowledge base.
  • ArgoCD health customizations validation, app health, and sync status checks.
  • Prometheus truncation awareness, resource sizing review, and EKS Auto Mode compliance.
  • Comprehensive health reporting with actionable recommendations for operators.

Quick Start

Run neb-cluster-health to generate a cluster health report; pass --remediate to auto-remediate actionable findings.

Frequently Asked Questions about neb-cluster-health

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

FAQPage Schema
How do I check Kubernetes cluster health and ArgoCD sync status?

To check Kubernetes cluster health and ArgoCD sync status, you can run a health check skill that identifies synchronization issues, validates ArgoCD health customizations, and reports app status against an operational knowledge base.

What is the best way to detect known flaky apps in ArgoCD managed clusters?

Detecting known flaky apps in ArgoCD managed clusters involves comparing current application states against a curated operational knowledge base to identify and report recurring synchronization or health anomalies.

How do I validate EKS Auto Mode compliance and resource sizing in Kubernetes?

Validating EKS Auto Mode compliance and resource sizing requires running live cluster checks that review resource allocations and verify AWS EKS Auto Mode configurations against expected operational standards.

Can I automatically remediate ArgoCD health and synchronization drift?

Yes, you can automatically remediate ArgoCD health and synchronization drift by passing a remediation flag to trigger a self-heal workflow, which applies actionable fixes for identified configuration and state issues.

Why does Prometheus truncation affect my Kubernetes monitoring names?

Prometheus truncation affects Kubernetes monitoring because metric naming constraints can clip long labels, causing alerting and dashboard mismatches that require specific awareness during cluster health reviews.

Do I need live cluster access to run ArgoCD health customizations checks?

Live cluster access is required to apply live checks for ArgoCD health customizations, but config-only checks can still validate known flaky apps and operational knowledge when direct cluster access is unavailable.