Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Guides business and IT teams through incident detection, severity classification, containment, resolution, communication, and post-mortem with automated time...
Guides business and IT teams through incident detection, severity classification, containment, resolution, communication, and post-mortem with automated time...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Structured incident response for business and IT teams. Guides you through detection, triage, containment, resolution, and post-mortem โ with auto-generated timelines and action items.
When triggered with an incident description, this skill: Classifies severity (P1-P4) based on impact and urgency Generates a response checklist tailored to incident type (outage, data breach, security event, service degradation, vendor failure) Builds a communication plan โ who to notify, when, what channels Creates a real-time timeline as you log updates Produces a post-mortem template with root cause analysis and prevention steps
Tell your agent about an incident: "Production API is returning 500 errors for 20% of requests. Started 10 minutes ago." Or trigger proactively: "Create an incident response plan for a potential data breach scenario"
Service outages โ full or partial downtime Security incidents โ breaches, unauthorized access, phishing Data incidents โ corruption, loss, privacy violations Vendor failures โ third-party SLA breaches Performance degradation โ latency spikes, capacity issues
LevelImpactResponse TimeEscalationP1 - CriticalBusiness stoppedImmediateExecutive + all handsP2 - HighMajor feature down< 30 minEngineering lead + PMP3 - MediumDegraded experience< 2 hoursOn-call teamP4 - LowMinor issueNext business dayTicket queue
Confirm the incident is real (not a false alarm) Classify severity using the matrix above Assign incident commander Open a dedicated communication channel
Identify blast radius โ what's affected? Apply immediate mitigation (rollback, feature flag, scaling) Communicate status to stakeholders
Root cause investigation Implement fix with verification Monitor for recurrence Update all stakeholders
Timeline of events Root cause analysis (5 Whys) What went well / what didn't Action items with owners and deadlines Process improvements
Works with any monitoring stack. Feed alerts from PagerDuty, Datadog, Grafana, or manual reports.
Pair this with a full AI Operations Context Pack for your industry. Pre-built incident taxonomies, compliance-aware escalation paths, and automated stakeholder templates. Browse packs: https://afrexai-cto.github.io/context-packs/ Free tools: AI Revenue Calculator: https://afrexai-cto.github.io/ai-revenue-calculator/ Agent Setup Wizard: https://afrexai-cto.github.io/agent-setup/
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.