Does it support specific technology stacks?

Yes, it is highly optimized for projects using Expo, Supabase, Vercel, and Stripe, providing specific log-querying and rollback guidance for these platforms.

How does this skill help during a live production outage?

It provides immediate structure by assigning roles, classifying severity, and offering time-boxed investigation paths and remediation steps for common failures in the Supabase and Vercel stack.

What is the focus of its post-mortem process?

It facilitates a blameless culture, focusing on how the system allowed a failure to occur rather than individual errors, resulting in a detailed timeline and actionable engineering tasks.

Can it help set up reliability metrics?

Absolutely. It can define Service Level Objectives (SLOs) and Service Level Indicators (SLIs) for your APIs and background workers to help manage your error budgets effectively.

Incident Response Commander

Name: Incident Response Commander
Author: coreymaypray

bycoreymaypray

0•

Analytics & Monitoring

Manages production outages and reliability engineering with structured protocols, blameless post-mortems, and stack-specific runbooks.

Incident Response Commander acts as a virtual SRE and incident lead, transforming production chaos into structured resolution. It specializes in defining severity levels, managing real-time outages, and building long-term reliability infrastructure like SLOs and automated runbooks. Specifically tuned for the Supabase, Vercel, and Stripe ecosystem, it ensures every incident results in a clear timeline and actionable, blameless post-mortem to prevent recurrence and reduce team burnout. By emphasizing mitigation over immediate root-cause searching, it helps engineering teams minimize MTTR and maintain high availability.

Key Features

01Automated incident severity classification (SEV1-SEV4) tailored to your stack

02SLO/SLI framework design and error budget policy implementation

030 GitHub stars

04Structured incident communication templates for Slack and status pages

05Stack-specific runbooks for Supabase, Vercel, and Stripe failure modes

06Blameless post-mortem facilitation with 5-Whys analysis and action tracking

Use Cases

01Conducting a systematic post-incident review to identify and fix systemic risks

02Rapidly mitigating a Supabase Edge Function failure or Vercel deployment outage

03Designing on-call rotations and escalation policies for small engineering teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add coreymaypray/sloth-skill-tree incident-response-commander

For use in Claude.ai and ChatGPT

Key Features

01Automated incident severity classification (SEV1-SEV4) tailored to your stack

02SLO/SLI framework design and error budget policy implementation

030 GitHub stars

04Structured incident communication templates for Slack and status pages

05Stack-specific runbooks for Supabase, Vercel, and Stripe failure modes

06Blameless post-mortem facilitation with 5-Whys analysis and action tracking

Use Cases

01Conducting a systematic post-incident review to identify and fix systemic risks

02Rapidly mitigating a Supabase Edge Function failure or Vercel deployment outage

03Designing on-call rotations and escalation policies for small engineering teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add coreymaypray/sloth-skill-tree incident-response-commander

For use in Claude.ai and ChatGPT