incident-runbook skillA
incident-runbook is agent-read markdown (skill) from andersonlimahw/lemon-ai-hub: Incident response runbooks, on-call workflows, and postmortem templates. Generates severity-tiered runbooks, communication templates, timeline reconstruction, and blameless postmortem docs. Use when user is in an incident, doing on-call prep, writing a postmortem, or building incident response playbooks..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Incident Runbook Structured incident response — from first alert to blameless postmortem. ## Quick Start ``` /incident-runbook new <service> — create runbook for a service /incident-runbook triage — immediate triage checklist /incident-runbook postmortem — generate postmortem from timeline /incident-runbook comms — draft stakeholder communication /incident-runbook playbook <error> — generate playbook for specific error type ``` ## Severity Matrix | Sev | Criteria | Response Time | Who | |-----|----------|---------------|-----| | **P0** | Prod down, data loss, security breach | 5 min | IC + Eng lead + CTO | | **P1** | Core feature degraded, >10% users affected | 15 min | IC + On-call | | **P2** | Non-critical feature degraded, workaround exists | 1 hour | On-call | | **P3** | Minor issue, low user impact | Next business day | Team | ## Immediate Response (First 15 Minutes) ``` [ ] 1. Acknowledge alert (prevents duplicate paging) [ ] 2. Assess severity → declare P0/P1/P2/P3 [ ] 3. P0/P1: Open incident Slack channel #inc-YYYY-MM-DD-<slug> [ ] 4. Assign Incident Commander (IC) — single decision owner [ ] 5. Start timeline doc (incident log) …
Read the whole file at its exact version.
How to install
mdr add andersonlimahw/lemon-ai-hub/incident-runbook@git:20260614.2f67b30mdr add andersonlimahw/lemon-ai-hub/incident-runbook@sha256:0dfcdc7f964feaecPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_76sc3xwn3refn2kk)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4977 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
andersonlimahw/lemon-ai-hub · 14 stars · license none · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_76sc3xwn3refn2kk GET https://markdownregistry.com/api/v1/resolve?ref=andersonlimahw/lemon-ai-hub/incident-runbook GET https://markdownregistry.com/api/v1/blob/0dfcdc7f964feaecdfc5c2cb39a46b65321aa4024657b29ce55f29ffd39efc4d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from andersonlimahw/lemon-ai-hub
Every file in andersonlimahw/lemon-ai-hub