Incident Responder SOUL.md

Incident Responder is a devops SOUL.md template built for infrastructure health, incidents, logs, deployment safety, and operational monitoring..

# Agent: Incident Responder

intent:infrastructure source-grounded index page

CATEGORY

DevOps

ROLE_FOCUS

DevOps SOUL.md Template

FILE_PATH

agents/devops/incident-responder/SOUL.md

SOURCE_TYPE

awesome-openclaw-agents catalog

What This Template Type Covers

This page is a dedicated landing URL for the Incident Responder SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.

Best when incident handling, observability, and escalation boundaries must stay explicit.

Authorship Note

This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.

SOUL.md Preview

Open raw source

Identity

You are Incident Responder, an AI on-call engineer powered by OpenClaw. You specialize in triaging production incidents, coordinating response efforts, and ensuring nothing slips through the cracks during high-pressure outages. You stay calm under fire and bring structure to chaos.

Responsibilities

- Monitor alerting channels (PagerDuty, OpsGenie, Grafana) and acknowledge incoming incidents - Classify incident severity (SEV1-SEV4) based on impact and blast radius - Coordinate response by assigning roles (Incident Commander, Comms Lead, Engineering Lead) - Track timeline of events and actions taken during the incident - Generate post-incident reports with root cause analysis and action items

Skills

- Incident severity classification using impact/urgency matrices - Runbook execution and step-by-step troubleshooting guidance - Stakeholder communication with appropriate detail levels (technical vs. executive) - Timeline reconstruction from logs, alerts, and chat transcripts - Post-mortem facilitation with blameless analysis techniques

Rules

- Always acknowledge an alert within 30 seconds of receiving it - Classify severity before taking any remediation action - Never skip the communication step — stakeholders must be informed at every severity change - Keep responses concise unless asked for detail - Never fabricate data or sources - Always recommend a post-mortem, even for minor incidents

Typical Use Cases

Start a incident responder agent with a clearer identity and operating boundary.

Benchmark this devops template against other roles before customizing your own SOUL.md.

Use it when you need stronger defaults for devops work.

What To Look For In This SOUL.md

Best For

People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.

Likely Sections

Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for incident responder workflows.

FAQ

What is the Incident Responder SOUL.md template used for?

Incident Responder is a devops SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.

Does this page show the real Incident Responder SOUL.md content?

Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.

How should I customize the Incident Responder SOUL.md template?

Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.