incident-response

Guide operators to gather signals, form a hypothesis, and test it with one diagnostic command.

482|100|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/agulli/atlas-agents --skill incident-response-agulli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/agulli/atlas-agents/tree/main/ch09_agent_skills/skills/incident-response
Command: npx skills add https://github.com/agulli/atlas-agents --skill incident-response-agulli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose production incidents quickly by guiding operators to gather signals, form a single hypothesis, and test it with one diagnostic command, reducing mean time to recovery.

Core Features & Use Cases

  • Structured incident triage: assess severity, gather signals, and form a single hypothesis.
  • Deterministic testing: run exactly one diagnostic command to confirm or refute the hypothesis.
  • Post-mortem discipline: generate a concise post-mortem with root cause and preventive actions.

Quick Start

Explain the current incident, gather signals, form a single hypothesis, and run one diagnostic command to test it.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I triage a production incident and reduce mean time to recovery?

Triage a production incident by gathering system signals to form a single, decisive hypothesis, then testing it with exactly one diagnostic command to reduce mean time to recovery.

What is the best way to diagnose latency degradation across services during an outage?

Diagnose latency degradation by assessing incident severity, gathering operational signals, forming a single hypothesis, and running one precise diagnostic command to validate the root cause.

How do I write a post-mortem for an on-call incident?

Write a post-mortem by documenting the tested diagnostic hypothesis, identifying the root cause, and outlining preventive actions to ensure disciplined incident management.

Can I run multiple diagnostic commands to troubleshoot bursty errors?

No, troubleshooting bursty errors requires running exactly one diagnostic command to confirm or refute your single hypothesis, avoiding risky changes during the incident.

When should I avoid forming multiple hypotheses during incident management?

Avoid multiple hypotheses during incident management when diagnosing outages; disciplined data collection and a single decisive hypothesis prevent scattered diagnostics and risky changes.