incident-commanderIncident Commander Skill
Install via ClawdBot CLI:
clawdbot install alirezarezvani/incident-commanderGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://bridge.company.com/incident-{level.lower(Audited Apr 17, 2026 · audit v1.0
Generated Mar 20, 2026
A major online retailer experiences a complete payment processing failure during peak holiday shopping. The Incident Commander skill classifies this as SEV1, establishes a war room, and coordinates between payment gateway engineers, fraud teams, and customer support to restore service while providing 15-minute stakeholder updates.
A SaaS provider's database cluster suffers latency spikes, affecting 30% of enterprise users. The skill classifies it as SEV2, uses the timeline reconstructor to correlate events from monitoring tools, and generates communication templates to keep customers informed every 30 minutes until performance is stabilized.
A banking application reports data inconsistencies in transaction records after a software update. The Incident Commander skill identifies this as SEV1 due to potential financial impact, coordinates rollback procedures with DevOps teams, and uses the PIR generator to apply a 5 Whys analysis for root cause identification.
A hospital's patient monitoring system triggers non-urgent alerts for logging gaps in a test environment. The skill classifies this as SEV4, assigns it for response within two business days via standard ticketing, and uses the incident classifier to recommend documentation updates without disrupting clinical operations.
Companies offering incident management as a service can integrate this skill to provide automated severity classification and PIR generation to clients, reducing manual effort and ensuring consistent response frameworks across customer organizations.
MSPs use the skill to standardize incident response for multiple client infrastructures, leveraging communication templates and runbook integration to handle diverse environments efficiently while maintaining compliance with SLAs.
Large organizations deploy the skill internally to streamline their SRE and DevOps teams' incident processes, reducing mean time to resolution and improving post-incident learning through structured reviews, often as part of broader IT service management platforms.
💬 Integration Tip
Integrate with existing monitoring tools like Datadog or Splunk to feed event data directly into the timeline reconstructor for automated incident narrative creation.
Scored Apr 19, 2026
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
A clean, reliable system resource monitor for CPU load, RAM, Swap, and Disk usage. Optimized for OpenClaw.
Build reliable backend services with proper error handling, security, and observability.
Monitor blood glucose via Dexcom G7/G6 CGM
Location awareness via privacy-friendly GPS tracking (Home Assistant, OwnTracks, GPS Logger). Set location-based reminders and ask about movement history, travel time, and nearby POIs.
Structured logging, distributed tracing, and metrics collection patterns for building observable systems. Use when implementing logging infrastructure, setting up distributed tracing with OpenTelemetry, designing metrics collection (RED/USE methods), configuring alerting and dashboards, or reviewing observability practices. Covers structured JSON logging, context propagation, trace sampling, Prometheus/Grafana stack, alert design, and PII/secret scrubbing.