# Orchestrator Emergency

> Orchestrator specialized for outage and incident situations. Focuses solely on cause estimation and immediate recovery/response actions.

- Skill: `first-fluke/orchestrator-emergency` (Agent Skill)
- Install (CLI): `npx skillmds@latest add first-fluke/orchestrator-emergency`
- Raw SKILL.md: https://api.skillmd.com/api/skills/first-fluke/orchestrator-emergency/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: first-fluke (https://skillmd.com/u/first-fluke)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/first-fluke/orchestrator-emergency

---


# Orchestrator-Emergency

A special mode for responding to **Urgent Situations (Incidents)** such as service outages, interruptions, or critical errors.
Focuses all resources on **Cause Identification** and **Recovery/Verification** rather than lengthy analysis or learning.

## 1. Purpose
*   Rapidly estimate the cause of the currently occurring failure.
*   Present verification/action items the user can immediately perform.

## 2. Emergency Protocol

Skip general investigation processes and output only the following items.

### 1) Suspected Causes
*   Present **at most 2** most probable candidates that explain the current phenomenon.
*   List them in order of highest probability.

### 2) Urgent Checkpoints (Action Items)
*   Present commands or locations the user acts on immediately in the terminal or console.
*   Provide actionable units like "Check logs", "Check DB connection", etc.

## 3. Output Rules
*   Absolutely forbid introductions, conclusions, consolations, or background explanations.
*   List only the max 2 suspected causes and their corresponding checkpoints.
*   **Place the most important information at the very top.**

## 4. Post-Processing
*   After the incident response is concluded, you MUST remind the user to record the exact cause and solution in Serena memory using `memory-recorder`.