rescue

Diagnoses and resolves production service incidents with structured triage workflows.

115|13|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Houseofmvps/ultraship --skill rescue-houseofmvps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rescue
Source: https://github.com/Houseofmvps/ultraship/tree/main/skills/rescue
Command: npx skills add https://github.com/Houseofmvps/ultraship --skill rescue-houseofmvps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production incidents cause immediate revenue loss, eroded user trust, and chaotic uncoordinated response efforts that prolong downtime and increase the risk of repeat failures.

Core Features & Use Cases

  • Structured Severity Classification: Automatically categorize incidents as SEV-1 through SEV-4 to prioritize response efforts appropriately.
  • End-to-End Incident Workflow: Guides teams through context gathering, diagnostic runs, triage, recovery, verification, communication, post-mortem generation, and preventive measure planning.
  • Tool Integration: Works with diagnostic scripts and Sentry for live production error data to pinpoint root causes faster.
  • Use Case: If your SaaS platform goes unresponsive during a product launch, this skill walks you through fast rollback or hotfix deployment, user communication, and a post-mortem to add missing test coverage and monitoring to avoid future outages.

Quick Start

Use the rescue skill to diagnose and recover from the current production outage at your provided URL.

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 to minimize downtime and prevent repeat incidents?

Resolve a production outage using a structured incident response workflow that handles triage, recovery, verification, and post-mortem generation. This process minimizes downtime and identifies preventive measures to avoid repeat incidents.

What is the best way to triage production errors using Sentry data?

Triage production errors by integrating Sentry live data with structured diagnostic scripts. This workflow pinpoints root causes faster and categorizes incident severity to prioritize response efforts appropriately.

How do I classify incident severity for an unresponsive SaaS platform during a launch?

Classify incident severity automatically from SEV-1 through SEV-4 to prioritize response efforts. This structured classification guides appropriate recovery actions for critical user-facing bugs and full outages.

Can I use this incident response workflow for cloud-hosted web APIs?

Yes, this incident response workflow applies to cloud-hosted web APIs and services. It guides SRE teams through diagnostic runs, fast rollback or hotfix deployment, and user communication during production issues.

How do I generate a post-mortem after resolving a critical service outage?

Generate a post-mortem after a service outage by following the end-to-end incident workflow. It documents context gathering, recovery actions, and recommends preventive measures like adding test coverage and monitoring.

Why does my engineering team need a structured incident response workflow for error spikes?

A structured incident response workflow prevents chaotic uncoordinated efforts that prolong downtime. It provides diagnostic tool integration and recovery option guidance to immediately address error spikes and revenue loss.