skills.rest
jay6697117
jay6697117COMMUNITY
Explore all skills by this author →
Website𝕏@nullGitHub

agency-incident-response-commander

Coordinate structured incident response with defined roles and runbooks.

Updated Mar 22, 2026
Search Tags:#post-mortem#reliability#on-call#runbooks#incident#incident-management
One-click install
npx skills add https://github.com/jay6697117/agency-agents-antigravity --skill agency-incident-response-commander
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-incident-response-commander
Source: https://github.com/jay6697117/agency-agents-antigravity/tree/main/.agents/skills/agency-incident-response-commander
Command: npx skills add https://github.com/jay6697117/agency-agents-antigravity --skill agency-incident-response-commander

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert incident commander specializing in production incident management, structured response coordination, post-mortem facilitation, SLO/SLI tracking, and on-call process design for reliable engineering organizations.

Core Features & Use Cases

  • Structured incident management with defined roles (Incident Commander, Communications Lead, Technical Lead, Scribe) and a scalable runbook library
  • On-call design, SLO/SLI frameworks, and runbooks for common failure modes, plus game days and chaos testing to validate reliability
  • Post-mortem facilitation and actionable follow-ups to close gaps and prevent recurrence

Quick Start

Initiate an incident as Incident Commander, assign roles, and follow the structured response workflow to restore service.

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 production outages across complex services?▼

Coordinate incident response by assigning structured roles like Incident Commander, Communications Lead, and Technical Lead, following a scalable runbook workflow to systematically restore service across complex services.

What is a blameless post-mortem and how do I facilitate one after an incident?▼

A blameless post-mortem is a structured review focusing on systemic gaps rather than individual fault. Facilitate post-mortem analysis to document actionable follow-ups and prevent incident recurrence across engineering teams.

Can I use this to create runbooks for common failure modes and validate them?▼

Yes, you can develop runbook templates for common failure modes and validate them through game days and chaos testing. This ensures your runbooks effectively guide incident management and reliability validation.

What roles are required for structured incident management in a reliable engineering organization?▼

Structured incident management requires defined roles: Incident Commander, Communications Lead, Technical Lead, and Scribe. These roles coordinate response efforts, document timelines, and drive technical resolution.

Related Skills

Explore More Software Engineering Skills→
omeraltnomeraltn

agency-incident-response-commander

Coordinate production incident response and post-mortem facilitation for distributed services.

Community
Advanced
camelranchentertainmentcamelranchentertainment
1

chaos-engineer

Design chaos experiments and resilience playbooks for distributed systems.

Community
Advanced
aaronbassettaaronbassett
4

flutter-core:flutter-serverpod

Build Flutter backends with Serverpod typed models, endpoints, and authentication.

Community
Advanced
augustoheissaugustoheiss

agency-incident-response-commander

Coordinate production incident response with roles, runbooks, and post-mortems.

Community
Advanced