s3-incident-runbooksCreate structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to...
Install via ClawdBot CLI:
clawdbot install solomonneas/s3-incident-runbooksGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://api.company.com/internal/feature-flagsCalls external URL not in known-safe list
https://grafana/d/paymentsAI Analysis
The skill contains example commands and URLs for incident response procedures, which are typical for runbook templates. The flagged external endpoints (e.g., Grafana dashboards, internal APIs) appear to be illustrative placeholders for monitoring tools, not active data exfiltration instructions. No evidence of credential harvesting, user intent override, or obfuscated malicious behavior was found.
Audited Apr 17, 2026 · audit v1.0
Generated Oct 5, 2026
A major online retailer experiences a complete failure of its payment processing service during a flash sale, causing checkout errors for all customers. The on-call engineer uses the runbook to quickly assess impact, rollback a recent deployment, and communicate with stakeholders.
A B2B SaaS provider notices elevated API latency and error rates affecting key features for enterprise clients. The runbook guides the team through triaging database performance, checking external dependencies, and implementing circuit breakers to restore service.
A digital payments company sees a spike in failed transactions due to a bug in a specific payment method. The runbook helps isolate the issue, disable the problematic feature via feature flag, and verify data integrity before resuming normal operations.
A healthcare technology firm suffers an outage in its patient data API, impacting access for clinics and hospitals. The runbook provides steps to assess scope, check recent changes, and escalate to the appropriate teams while maintaining compliance.
A multiplayer gaming platform faces a traffic surge from a popular event, causing server overload and lag for players. The runbook enables rapid scaling, rate limiting, and blocking of suspicious traffic to stabilize the service.
Companies offer cloud-based software on a recurring subscription basis, requiring high availability and rapid incident response to maintain customer trust and minimize churn. Runbooks ensure consistent handling of outages and degradations.
Businesses like payment processors or marketplaces earn fees per transaction, making uptime critical for revenue. Incident runbooks help quickly resolve issues that could block transactions and cause financial losses.
Services offer a free tier with paid premium plans that include SLA-backed support. Runbooks are essential for on-call engineers to meet strict response times and avoid penalties, while also handling incidents for free users efficiently.
💬 Integration Tip
Customize the runbook templates with your specific service names, metrics, and escalation paths to make them directly actionable. Integrate with your alerting and communication tools (e.g., PagerDuty, Slack) to automate initial steps and reduce response time.
Scored Jun 29, 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.