incident-response-runbookCreate, maintain, and execute detailed incident response runbooks to guide triage, communication, and post-incident reviews for production outages.
Install via ClawdBot CLI:
clawdbot install charlie-morrison/incident-response-runbookGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 8, 2026
A major online retailer experiences a SEV1 outage on its payment and checkout services during peak holiday traffic. The incident response team uses the runbook to triage database connection pool exhaustion, roll back a recent deployment, and communicate status updates to customers and executives. Post-incident, they generate a blameless review to prevent recurrence.
A B2B SaaS company detects elevated API latency and error rates impacting multiple enterprise customers. The on-call engineer follows the runbook to diagnose a memory leak in worker processes, apply a hotfix, and coordinate with account managers for customer communication. The incident is documented for SLA reporting and future runbook improvements.
A digital banking app suffers a SEV2 incident when an upstream authentication provider goes down, blocking user logins. The incident team uses the runbook to assess blast radius, activate fallback authentication, and post status updates. After resolution, they conduct a post-mortem to evaluate vendor risk and update escalation procedures.
A healthcare analytics platform experiences a data ingestion failure, delaying critical patient reports for hospitals. The runbook guides the team through triage, root cause analysis (misconfigured message queue), and failover to a backup pipeline. A post-incident review ensures compliance and improves data reliability.
A game studio's multiplayer servers crash under unexpected load on launch day, causing a SEV1 outage. Engineers use the runbook to scale infrastructure, mitigate a matchmaking service bug, and communicate via social media. The post-incident review captures lessons for capacity planning and future launches.
A cloud service that provides automated runbook generation, real-time incident triage, and post-incident review tools to engineering teams. It integrates with monitoring and communication tools to streamline incident response. Revenue comes from monthly per-seat subscriptions.
Expert consultants help organizations build custom incident response runbooks, conduct training exercises, and facilitate post-incident reviews. They offer tailored solutions for compliance-heavy industries like finance and healthcare. Revenue is generated through project-based fees and retainers.
A free open-source core tool for generating runbooks is offered to attract users, with a paid tier that adds advanced features like AI-driven triage, integration with enterprise systems, and 24/7 support. Upsell targets growing engineering teams. Revenue from premium licenses and support contracts.
💬 Integration Tip
Integrate with monitoring tools (Datadog, Prometheus) and communication platforms (Slack, PagerDuty) to automate alerting and runbook execution. Use the provided script to generate service-specific runbooks from metadata, and customize templates to match your organization's incident workflow.
Scored Oct 8, 2026
Firecrawl CLI for web scraping, crawling, and search. Scrape single pages or entire websites, map site URLs, and search the web with full content extraction. Returns clean markdown optimized for LLM context. Use for research, documentation extraction, competitive intelligence, and content monitoring.
Incident Commander Skill
Monitors OpenClaw cron job health, identifies failures, timeouts, and delivery issues.
Observability Designer (POWERFUL)
Use when defining SLIs/SLOs, managing error budgets, or building reliable systems at scale. Invoke for incident management, chaos engineering, toil reduction, capacity planning.
QQ bot integration for OpenClaw with session isolation, logging, and AI auto-reply. Supports private chat and group @messages.