rescue

Diagnose production incidents and guide recovery workflows.

4|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anderson-0/mighty-powers --skill rescue-anderson-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rescue
Source: https://github.com/anderson-0/mighty-powers/tree/main/skills/rescue
Command: npx skills add https://github.com/anderson-0/mighty-powers --skill rescue-anderson-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams rapidly diagnose and recover from production incidents by providing a structured incident response process for outages, degraded services, and critical bugs.

Core Features & Use Cases

  • Incident Triage: Classifies severity, gathers critical context, and prioritizes restoration efforts during production failures.
  • Recovery Workflow: Guides diagnostics, rollback decisions, hot fixes, verification steps, and incident communication.
  • Post-Incident Prevention: Creates post-mortems and recommends monitoring, testing, and process improvements to prevent recurrence.

Quick Start

Ask the rescue skill to investigate a production outage, identify the root cause, and guide the recovery process.

Frequently Asked Questions about rescue

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

FAQPage Schema
How do I handle a production outage and restore my service?

To handle a production outage, you need structured incident response for triage, diagnostics, and recovery. This involves classifying severity, gathering context, deciding on rollbacks or hot fixes, and verifying system health to restore service.

What is the process for incident triage during degraded system performance?

Incident triage for degraded systems involves classifying the severity of performance drops, gathering critical operational context, and prioritizing restoration efforts to stabilize the application before executing a full recovery workflow.

How do I write a postmortem after resolving a critical user-facing bug?

Writing a postmortem after a critical bug involves documenting the incident timeline, identifying root causes, and recommending monitoring, testing, and process improvements to establish post-incident prevention practices.

Can I use a structured workflow for failed deployment rollback decisions?

Yes, you can use a structured incident response workflow to guide failed deployment rollback decisions. It evaluates diagnostics, plans recovery actions, verifies health post-rollback, and provides communication templates for stakeholders.

Does incident response work for error spikes in production environments?

Incident response applies to error spikes in production by applying diagnostic analysis to identify root causes, executing recovery planning to mitigate the errors, and verifying system health to ensure full service restoration.

What's the best way to communicate with stakeholders during an SRE incident response?

The best way to communicate during an SRE incident response is using structured communication templates that provide consistent updates on triage status, recovery progress, and health verification throughout the production failure.