incident-response

Automate production incident triage, stabilization, and postmortem documentation.

Updated May 11, 2026
One-click install
npx skills add https://github.com/resultakak/argos --skill incident-response-resultakak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/resultakak/argos/tree/main/skills/incident-response
Command: npx skills add https://github.com/resultakak/argos --skill incident-response-resultakak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production incidents triage, stabilization, forensics, and postmortem discipline to minimize MTTR and improve reliability.

Core Features & Use Cases

  • Structured incident triage and role delegation
  • Stabilization workflows with rollback and containment guidance
  • Forensics data capture, evidence snapshots, and postmortem templates
  • Transparent internal/external communications and status updates

Quick Start

Initiate the incident-response workflow to triage, stabilize, and document a postmortem.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I automate incident triage and stabilization for production outages?

Automate incident triage by applying structured workflows for alert-driven outages and latency spikes, enforcing role delegation like incident commander to stabilize systems, capture forensic data, and reduce MTTR.

What is the best way to structure incident response roles during a live system outage?

Structure incident response using defined roles such as incident commander and on-call responders to coordinate alert-driven outages, enforce escalation protocols, and manage stabilization workflows across live systems.

How do I capture forensics and create blameless postmortem templates after a security incident?

Capture forensics by taking evidence snapshots during the incident, then generate blameless postmortem templates to document security incidents, ensure traceability, and drive reliability improvements.

Can I use this incident response workflow for data inconsistencies and latency spikes?

Yes, the incident response workflow applies to data inconsistencies, latency spikes, alert-driven outages, and security incidents, providing stabilization workflows and containment guidance across live systems.

How do I manage internal and external status communications during an active incident?

Manage communications by enforcing transparent internal and external status updates throughout the incident lifecycle, ensuring controlled responses and clear escalation protocols during alert-driven outages.

What should I do if rollback and containment guidance is not working for a live system incident?

If rollback and containment guidance fails, escalate through the incident commander role to apply advanced stabilization workflows, capture forensic data snapshots, and maintain traceability for postmortem analysis.