Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When building incident response runbooks for outages (e.g., payment systems), database incident procedures, onboarding on-call engineers, or standardizing escalation across teams.
references/details.md for deeper patternsA structured, actionable runbook with step-by-step recovery, escalation matrix, and communication templates that reduce MTTR and help 3 AM responders act confidently.
Use Cases
A platform team needs a runbook for payment processing outages. Using this skill, they generate a SEV1–SEV4 graded procedure with detection alerts, mitigation steps, rollback, and an escalation matrix. New on-call engineers follow the 3 AM-friendly checklist to restore service within SLA, reducing panic and MTTR.
Multiple engineering teams use inconsistent escalation. The skill standardizes a cross-team escalation matrix and communication templates, with metadata and CI validation. On-call handoffs become smoother and stakeholders get timely updates via the dedicated communicator role defined in the runbook.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File