sre-agent

Automate PagerDuty alert triage, root cause analysis, and proactive patrol workflows.

42|7|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/addxai/enterprise-harness-engineering --skill sre-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-agent
Source: https://github.com/addxai/enterprise-harness-engineering/tree/main/skills/sre-agent
Command: npx skills add https://github.com/addxai/enterprise-harness-engineering --skill sre-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

SRE teams often face slow, manual oncall response, missed early warning signs of outages, and inconsistent root cause analysis that leads to repeated incidents. This Skill automates the entire SRE operational workflow, from alert triage and oncall management to proactive patrol and continuous self-improvement, reducing mean time to resolution and preventing outages before they impact users.

Core Features & Use Cases

  • 4 Operating Modes: Oncall (automated PagerDuty alert polling, triage, and notification), Diagnosis (multi-dimensional root cause analysis across Prometheus, Kubernetes, cloud CLIs, and logs), Patrol (proactive trend-based health checks to catch issues before they fire alerts), and Iteration (self-improvement based on incident retrospectives to boost diagnostic accuracy over time).
  • PagerDuty Integration: Native support for alert querying, correlation, and (with explicit confirmation) acknowledge/resolve operations, with anti-hallucination confirmation loops to prevent accidental changes.
  • Proactive Patrol: Trend analysis across 24h and 7d windows, fault tolerance verification, and resource limit checks to identify at-risk systems before they fail.
  • Use Case: An SRE oncall engineer can use this Skill to automatically pull all triggered PagerDuty alerts, triage and correlate them, run parallel root cause analysis across multiple data sources, and send structured incident reports to team notification channels — all without manual intervention.

Quick Start

Use the sre-agent skill to start an oncall shift, automatically triage all current PagerDuty alerts, and run root cause analysis for any triggered incidents.

Frequently Asked Questions about sre-agent

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

FAQPage Schema
How do I automate PagerDuty alert triage and root cause analysis for oncall shifts?

Automating PagerDuty alert triage involves polling triggered alerts, correlating them, and running multi-dimensional root cause analysis across Prometheus, Kubernetes, and cloud CLIs to reduce mean time to resolution without manual intervention.

What is proactive SRE patrol and how does it prevent production outages?

Proactive SRE patrol performs trend-based health checks across 24h and 7d windows to identify at-risk systems, verify fault tolerance, and catch issues before they trigger alerts and impact users.

Can I use this automated incident diagnosis workflow with Prometheus and Kubernetes?

Yes, the incident diagnosis workflow integrates natively with Prometheus and Kubernetes to query metrics and cluster state, running parallel root cause analysis across multiple data sources for comprehensive alert triage.

How do I send automated incident reports to Feishu notification webhooks during oncall?

You can send structured incident reports to Feishu notification webhooks by automating the alert triage workflow, which correlates PagerDuty alerts and pushes diagnostic results directly to team channels.

Does automated SRE oncall support acknowledge and resolve operations in PagerDuty?

Yes, the workflow supports querying, acknowledging, and resolving PagerDuty alerts, but it uses anti-hallucination confirmation loops to require explicit user confirmation before applying any state changes.

What is the best way to improve diagnostic accuracy for repeated incident root cause analysis?

The best way to improve diagnostic accuracy is leveraging incident retrospectives through an iteration mode, which continuously self-improves diagnostic matching and root cause analysis based on past incident patterns.