alert-rca

Identify alert root causes by analyzing multi-source data and reconstructing incident timelines.

59|4|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/yuki-aigc/pomelobot --skill alert-rca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alert-rca
Source: https://github.com/yuki-aigc/pomelobot/tree/main/workspace/skills/alert-rca
Command: npx skills add https://github.com/yuki-aigc/pomelobot --skill alert-rca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

告警事故根因定位通过系统化分析告警事件和多源数据关联分析,快速定位根因、重建事故时间线并提供可执行的修复建议。

Core Features & Use Cases

  • 多源数据关联:整合日志、指标、链路、事件等信息,帮助从不同角度洞察故障
  • 时间线重建与因果分析:按时间顺序重建事故过程并识别核心转折点
  • 根因定位与修复建议:给出可操作的根因结论和纠正措施,支持后续预防
  • 适用场景:突发告警响应、故障复盘、告警关联分析、慢性问题诊断、容量定位

Quick Start

Analyze the provided alert data and generate a structured root-cause analysis report with a timeline and remediation steps.

Frequently Asked Questions about alert-rca

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

FAQPage Schema
How do I identify the root cause of an alert across multiple data sources?

Reconstructing an incident timeline requires sequencing logs, metrics, traces, and events chronologically. This process identifies core turning points and causal relationships during cross-service investigations and P0/P1 alert responses.

What is the best way to perform root-cause analysis for a P0 incident postmortem?

Root-cause analysis for a P0 incident postmortem involves systematically correlating multi-source data to validate failure hypotheses. It generates a structured report with actionable remediation guidance to support subsequent prevention.

How do I generate actionable remediation steps after an alert is triggered?

To generate actionable remediation steps after an alert is triggered, analyze the reconstructed incident timeline and identified root cause. This yields corrective measures and structured guidance for incident response and prevention.

Can I use this approach for cross-service incident investigations and chronic problem diagnosis?

Yes, you can use this approach for cross-service incident investigations and chronic problem diagnosis. It applies end-to-end data collection and correlation to track complex dependencies and pinpoint elusive systemic failures.

Does alert root-cause analysis work without integrating logs, metrics, and traces?

Alert root-cause analysis relies heavily on integrating logs, metrics, and traces. Without these multi-source data inputs, reconstructing the incident timeline and accurately validating causal hypotheses for effective remediation is severely limited.