Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.
Start a fresh conversation. Replace the highlighted placeholders.
Use rescue to triage [incident or alignment issue description] and provide a recovery plan. If this is a technical fire, identify the blast radius, name current unknowns, and propose the minimum safe change for stabilization. If this is a trust or alignment issue, provide a neutral alignment check proposal based on observed signals and the agreed cadence. [Citations: primary L3, dependency_2 L7-8, L9-25, L27-34]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: rescuedescription: Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.
rescue
Purpose
A recovery plan and evidence of authorized mitigation.
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Principles
Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.