skills.rest
RHEcosystemAppEng
RHEcosystemAppEngOFFICIAL
Explore all skills by this author →
GitHub

incident-triage

Automate incident triage and root cause analysis for OpenShift clusters.

48|31|Updated Feb 2, 2026
Search Tags:#root cause analysis#remediation#Kubernetes#OpenShift#incident investigation
One-click install
npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill incident-triage-rhecosystemappeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-triage
Source: https://github.com/RHEcosystemAppEng/agentic-plugins/tree/main/rh-developer/skills/incident-triage
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill incident-triage-rhecosystemappeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openshift, observability, resources_get, resources_list, pods_list, pods_log, events_list, prometheus_query, prometheus_query_range, alertmanager_alerts, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of incident investigation in OpenShift by automating the collection of context, analysis, and root cause analysis, providing actionable remediation steps.

Core Features & Use Cases

  • Automated Incident Triage: Gather context and diagnose issues across multiple resources.
  • Root Cause Analysis: Use the Five Whys methodology to pinpoint the root cause of incidents.
  • Remediation Guidance: Offer targeted remediation commands based on findings.
  • Use Case: For an alert indicating high CPU usage, this Skill can automatically diagnose the issue, trace it back to the root cause, and suggest a fix.

Quick Start

Run the /incident-triage command with the necessary context to investigate an incident in OpenShift.

Frequently Asked Questions about incident-triage

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

FAQPage Schema
How do I automate root cause analysis for OpenShift incidents?▼

Automate OpenShift incident root cause analysis by gathering cluster context, querying Prometheus metrics, and applying the Five Whys methodology to pinpoint issues and suggest targeted remediation commands.

What is the best way to investigate Kubernetes pod alerts and high CPU usage?▼

Investigate Kubernetes pod alerts and high CPU usage by automating context collection across cluster resources, analyzing Prometheus metrics, and tracing symptoms back to their root cause for actionable fixes.

Can I use Prometheus metrics to diagnose OpenShift cluster issues?▼

Yes, you can diagnose OpenShift cluster issues by querying Prometheus metrics and Alertmanager alerts alongside Kubernetes API data to gather context and identify the root cause of incidents.

How do I troubleshoot OpenShift events when an incident occurs?▼

Troubleshoot OpenShift incidents by listing cluster events, querying pod logs, and analyzing resource metrics to automate context gathering and receive guided remediation steps for the identified failure.

Do I need cluster access to run automated incident triage in Kubernetes?▼

Yes, automated incident triage requires OpenShift cluster access and appropriate permissions to query resources, retrieve pod logs, list events, and execute Prometheus metric queries for accurate diagnosis.

What are the limitations of using Five Whys for Kubernetes incident investigation?▼

Using Five Whys for Kubernetes incident investigation relies on the accuracy of gathered cluster context, pod logs, and Prometheus metrics, meaning incomplete cluster access or missing telemetry can limit root cause accuracy.

Related Skills

Explore More Software Engineering Skills→
shepard-systemshepard-system
70

obs-alerts

Retrieve active alerts, silences, and Prometheus rule states via Alertmanager and Prometheus APIs.

Official
Intermediate
kcns008kcns008
3

k8s-troubleshooting

Diagnose and remediate Kubernetes and OpenShift cluster issues with a repeatable workflow.

Community
Advanced
dmzoneilldmzoneill
2

investigate-alert

Investigate firing Prometheus alerts by gathering pod health, events, and Kibana logs.

Community
Advanced
openoctaopenocta
3.1k

Prometheus Analysis

The quick brown fox jumps over the lazy dog.

Community
Intermediate