acm-cluster-health

Diagnose ACM hub cluster health using a 12-layer model and evidence tiers.

3|4|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/stolostron/acm-ai-qe --skill acm-cluster-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acm-cluster-health
Source: https://github.com/stolostron/acm-ai-qe/tree/main/.claude/skills/acm-cluster-health
Command: npx skills add https://github.com/stolostron/acm-ai-qe --skill acm-cluster-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires acm-search, acm-kubectl, neo4j-rhacm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a comprehensive health assessment of ACM hub clusters, enabling users to identify and diagnose issues within the cluster's infrastructure and applications.

Core Features & Use Cases

  • 12-Layer Diagnostic Model: Offers a systematic approach to cluster health assessment, covering compute, control plane, network, storage, configuration, authentication, RBAC, webhooks, operators, cross-cluster, data flow, and UI layers.
  • Trap Detection: Identifies common pitfalls that can lead to misdiagnosis, such as stale MCH/MCE operators or console plugin backend crashes.
  • Dependency Chain Verification: Provides a framework to trace symptoms to their root causes by following component dependencies.
  • Evidence Tier Framework: Uses a tiered system to weigh the reliability of evidence in conclusions.
  • MCP Tools: Integrates with acm-search, acm-kubectl, and neo4j-rhacm for enhanced diagnostics.
  • Quick Sanity Mode: Offers a lightweight health check for quick go/no-go assessments.

Quick Start

Run the 'acm-cluster-health' skill to perform a comprehensive health check on your ACM hub cluster.

Frequently Asked Questions about acm-cluster-health

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

FAQPage Schema
How do I diagnose ACM hub cluster health issues across infrastructure and applications?

Assessing ACM hub cluster health involves running a 12-layer diagnostic model that evaluates compute, control plane, network, storage, authentication, RBAC, webhooks, and operators. It applies trap detection and dependency chain verification to trace symptoms to root causes.

What is the best way to perform a quick go or no go health check on an ACM cluster?

The best way to perform a quick health check on an ACM cluster is using the Quick Sanity Mode, a lightweight assessment providing a rapid go or no go evaluation without running the full 12-layer diagnostic model.

Do I need oc CLI access to run a comprehensive ACM hub cluster health assessment?

Yes, oc CLI access to the ACM hub cluster is required to run a comprehensive health assessment. Optional MCPs including acm-search, acm-kubectl, and neo4j-rhacm can be integrated for enhanced diagnostic capabilities.

Why does my ACM cluster health diagnostic report stale MCH or MCE operators?

Your ACM cluster health diagnostic identifies stale MCH or MCE operators through trap detection, a feature that flags common pitfalls causing misdiagnosis. It ensures component dependencies are verified before concluding root causes.

Can I trace ACM cluster application symptoms back to their root causes using a dependency chain?

Yes, you can trace ACM cluster application symptoms to root causes using dependency chain verification. This framework follows component dependencies and applies an evidence tier system to weigh the reliability of diagnostic conclusions.