incident-commander

What This Skill Does

The Incident Commander skill provides a robust, professional-grade framework for managing technical service disruptions. Designed for Engineering and DevOps teams, it acts as an automated triage officer and documentation assistant. By centralizing incident response, it ensures that teams follow standardized protocols—from initial SEV classification and war-room setup to the final post-incident review (PIR). It automates the tedious parts of incident management, such as reconstructing chronologies from fragmented logs and drafting structured reports, allowing engineers to focus on technical resolution rather than administrative overhead.

Installation

To integrate this skill into your OpenClaw environment, use the following CLI command: clawhub install openclaw/skills/skills/alirezarezvani/incident-commander Ensure your local environment is configured with access to your relevant logging and alerting APIs for full integration capabilities.

Use Cases

• Real-time Incident Triage: Quickly classify incoming alerts as SEV1 or SEV2 to trigger the appropriate response protocols.
• Timeline Reconstruction: Ingest raw error logs and chat history to create a single source of truth for post-mortem analysis.
• Structured Learning: Generate professional post-incident reports using established methodologies like the 5 Whys or Fishbone diagrams.
• Stakeholder Updates: Standardize communication for executive summaries and public status page updates to minimize confusion during high-pressure events.

Example Prompts

1. "OpenClaw, start an incident session for the current database latency issue. Analyze the logs provided in the chat and classify the severity."
2. "Draft a SEV1 incident summary for the stakeholders based on the last 30 minutes of war-room activity and the current resolution status."
3. "Generate a PIR document using the 5 Whys framework for the outage that occurred between 02:00 and 03:00 UTC today."

Tips & Limitations

• Proactive Setup: Configure your log inputs before an incident occurs to ensure the Timeline Reconstructor has sufficient data to process.
• Human Oversight: While the skill automates reporting, always have a human Incident Commander review communication templates before they are sent to external stakeholders.
• Data Privacy: Be mindful of sensitive data in logs; ensure PII is masked before processing if your company policy mandates it. The tool functions best when paired with clear operational runbooks.