acm-cluster-investigator

Diagnose ACM test failures using the 12-layer diagnostic model.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill performs deep-dive investigations of individual ACM test failures, analyzing symptoms through infrastructure layers to identify root causes.

Core Features & Use Cases

  • 12-Layer Diagnostic Model: Analyzes failures through a comprehensive model, covering UI, Data Flow, Operators, and more.
  • Cluster Access & MCP Integration: Uses oc CLI for read-only cluster operations and integrates with MCP for enhanced context and verification.
  • Standalone Operation: Works independently with test failure data, or as part of the acm-failure-classifier Skill.

Quick Start

Use the acm-cluster-investigator skill to investigate a test failure with 'oc get events -n <ns> --sort-by=.lastTimestamp'.

Frequently Asked Questions about acm-cluster-investigator

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

FAQPage Schema
How do I perform root cause analysis on ACM test failures?

Root cause analysis of ACM test failures is conducted using a 12-layer diagnostic model that examines symptoms across infrastructure layers, utilizing oc CLI commands and MCP integrations to identify the underlying issue.

How does the 12-layer diagnostic model investigate cluster health?

The 12-layer diagnostic model investigates cluster health by analyzing test failure symptoms sequentially through comprehensive infrastructure layers, including UI, Data Flow, and Operators, to pinpoint the exact root cause.

Can I use oc CLI commands to diagnose test failures without modifying the cluster?

You can use oc CLI commands to diagnose test failures because the investigation operates strictly in read-only mode on clusters, ensuring that diagnostic data gathering does not modify your environment.

Does the diagnostic model require MCP integration to analyze cluster health?

MCP integration is not strictly required to analyze cluster health, but it is supported to provide enhanced context and verification during the root cause analysis of ACM test failures.

What is the best way to start investigating ACM test failures with oc CLI?

The best way to start investigating ACM test failures is by running 'oc get events' sorted by timestamp, which provides initial diagnostic data for the 12-layer model to analyze.