Incident Responder

Triage production alerts and coordinate structured incident response with severity classification.

110|18|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill incident-responder-travisleeeeee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Incident Responder
Source: https://github.com/TravisLeeeeee/awesome-openclaw-personas/tree/main/personas/devops/incident-responder
Command: npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill incident-responder-travisleeeeee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams respond quickly and consistently to production alerts by enforcing clear severity triage, coordinated action, and reliable incident documentation.

Core Features & Use Cases

  • Incident severity classification: Assigns SEV1–SEV4 based on impact and blast radius before remediation begins.
  • Structured response coordination: Guides role assignment for Incident Commander, Comms Lead, and Engineering Lead while maintaining a clear process.
  • Operational reporting: Reconstructs timelines and produces post-incident reports with root cause analysis and action items for follow-up.

Quick Start

Ask: "Acknowledge this alert and classify severity for the incident, then propose immediate actions and an initial stakeholder update plan."

Frequently Asked Questions about Incident Responder

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

FAQPage Schema
How do I classify incident severity for production alerts?

Incident severity classification assigns SEV1–SEV4 levels based on impact and blast radius before remediation begins. This ensures appropriate response allocation and stakeholder communication protocols are triggered for each specific severity tier.

What is the best way to coordinate roles during incident response?

Structured response coordination assigns specific roles like Incident Commander, Comms Lead, and Engineering Lead during incident response. This maintains clear process ownership and enables concurrent technical remediation and stakeholder communication updates.

How do I write a blameless post-mortem after resolving an incident?

Blameless post-mortem generation reconstructs incident timelines and produces reports containing root cause analysis and follow-up action items. This documentation reduces recurrence by focusing on systemic improvements rather than individual accountability.

How do I maintain stakeholder communication during an active incident?

Stakeholder communication during an incident is maintained by providing stepwise guidance and generating updates at each severity change. This ensures stakeholders receive consistent information regarding incident status and remediation progress.

Can I use this for on-call triage and SRE runbook workflows?

Yes, this handles on-call triage workflows involving alert acknowledgment and SRE runbook execution. It provides concise, stepwise guidance for triaging production alerts and coordinating structured response to restore service.

What are the limitations of automated incident timeline reconstruction?

Incident timeline reconstruction relies on documented alert acknowledgments and severity changes logged during the response. Incomplete or manual documentation during active incident management may result in fragmented or inaccurate timeline reconstruction.