skills.rest
anavvanzin
anavvanzinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agency-incident-response-commander

Coordinate production incident response with severity classification and blameless post-mortems.

Updated Apr 15, 2026
Search Tags:#post-mortem#on-call#runbooks#severity#incident#response#slo-sli
One-click install
npx skills add https://github.com/anavvanzin/Research --skill agency-incident-response-commander-anavvanzin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-incident-response-commander
Source: https://github.com/anavvanzin/Research/tree/main/cowork/integrations/antigravity/agency-incident-response-commander
Command: npx skills add https://github.com/anavvanzin/Research --skill agency-incident-response-commander-anavvanzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates production incident response, defines severity frameworks, facilitates blameless post-mortems, and designs on-call processes to keep systems reliable and teams resilient.

Core Features & Use Cases

  • Establish and enforce severity classification (SEV1–SEV4) with clear escalation triggers
  • Coordinate real-time incident response with defined roles: Incident Commander, Communications Lead, Technical Lead, Scribe
  • Facilitate blameless post-mortems and maintain an incident knowledge base
  • Design and maintain runbooks, SLO/SLI/SLA frameworks, and runbook-driven drills (game days)
  • Integrate incident tooling integrations and stakeholder communications templates

Quick Start

Declare an incident as SEV1, assign IC, Communications Lead, Technical Lead, and Scribe, and begin following the structured runbook to coordinate response

Frequently Asked Questions about agency-incident-response-commander

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

FAQPage Schema
How do I coordinate incident response for a multi-service outage?▼

Incident response coordination for multi-service outages uses defined roles like Incident Commander, Technical Lead, and Scribe to manage real-time mitigation efforts and reduce MTTR. You declare a severity level and follow structured runbooks to guide the response.

What is the best way to classify incident severity during an on-call rotation?▼

Classifying incident severity involves applying a SEV1 through SEV4 framework with clear escalation triggers. This structure determines the required response urgency, stakeholder communications, and resource allocation during production incidents.

How do I facilitate a blameless post-mortem after a production incident?▼

Facilitating a blameless post-mortem uses provided templates to document the incident timeline, identify root causes without assigning individual fault, and generate structured action items to improve system reliability.

Can I use SLO and SLI frameworks to design runbook-driven game day drills?▼

Yes, you can design SLO and SLI frameworks alongside runbook-driven game day drills. This approach tests system resilience and validates incident response procedures against reliability targets under controlled conditions.

Does incident command work for distributed systems with complex stakeholder communications?▼

Yes, incident command is designed for distributed systems and includes stakeholder communications templates. A dedicated Communications Lead manages external and internal updates, allowing the Technical Lead to focus on system restoration.

Related Skills

Explore More Software Engineering Skills→
daemon-blockint-techdaemon-blockint-tech
7

site-reliability-engineer

Define SLI/SLO targets and burn-rate policies for production reliability.

Community
Advanced
JayRHaJayRHa
3

incident-postmortem

Generate blameless postmortems with timelines, root causes, and owner-dated action items.

Community
Advanced
1479089714790897
7

kwp-engineering-incident-response

Manage incident response lifecycle with triage, status updates, and postmortem generation.

Community
Advanced
florianhornerflorianhorner
4

canary

Monitor live web apps for console errors and page failures after deployment.

Community
Advanced