incident

Coordinate triage, diagnosis, recovery, and documentation for production incidents.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/marcmunoz-uno/jailbreak --skill incident-marcmunoz-uno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/marcmunoz-uno/jailbreak/tree/main/skills/incident
Command: npx skills add https://github.com/marcmunoz-uno/jailbreak --skill incident-marcmunoz-uno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams respond when production is down or degraded by coordinating triage, diagnosis, fastest safe recovery, verification, and documentation so service disruption ends quickly and root causes are fixed.

Core Features & Use Cases

  • Rapid triage and severity classification: Quickly assess symptoms, blast radius, start time, and recent changes to label the incident as SEV1–SEV4.
  • Guided diagnosis and fastest safe remediation: Investigate logs, processes, resources, dependencies, and configuration to identify the root cause or best hypothesis, then apply an immediate recovery fix such as rollback, restore, restart, or failover.
  • Recovery verification and permanent follow-up: Validate health and core functionality via monitoring, then escalate to a permanent fix plan using an architect when a bandaid was applied.

Quick Start

Use the incident skill when you see a production outage or major degradation and need an end-to-end response from triage through verification and incident documentation.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I coordinate production incident triage and service recovery during an outage?

Production incident triage is coordinated by spawning dedicated responder agents that assess symptoms, classify severity from SEV1 to SEV4, and apply the fastest safe remediation like rollback or restart to restore service.

What is the best way to perform root cause analysis during API downtime or failing cron jobs?

Root cause analysis during API downtime or failing cron jobs is performed by investigating logs, processes, resources, and dependencies to identify the failure source, then applying an immediate recovery fix before escalating to a permanent fix plan.

How do I verify service recovery and document a post-incident report after a rollback?

Service recovery is verified by validating health and core functionality via monitoring after a rollback, followed by generating a structured incident report that documents the triage, diagnosis, and permanent fix plan.

Can I use this incident response workflow for broken configurations and resource failures?

This incident response workflow supports broken configurations and resource failures by applying a severity-based workflow with explicit stop conditions to guide diagnosis, recovery, and verification across various production degradation scenarios.

When should I escalate a bandaid fix to a permanent fix plan during incident management?

You should escalate a bandaid fix to a permanent fix plan during incident management when an immediate recovery action like a rollback or failover was applied, requiring an architect agent to design a permanent solution.

Does this incident triage process require dependencies or external components to function?

This incident triage process requires no external dependencies or components, operating independently by spawning its own dedicated responder agents to execute the severity-based workflow from triage through documentation.