Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
Post-Mortem & Incident Review
Guide structured, blameless post-mortems with root cause analysis, action tracking, and prevention steps to reduce repeat production incidents and outages.
skill openclawclawhub Free
Guide structured, blameless post-mortems with root cause analysis, action tracking, and prevention steps to reduce repeat production incidents and outages.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- 1kalin
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Post-Mortem & Incident Review Framework
Run structured post-mortems that actually prevent repeat failures. Blameless analysis, root cause identification, and action tracking.
When to Use
After any production incident, outage, or service degradation After a missed deadline, failed launch, or lost deal After any event costing >$5K or >4 hours of team time Quarterly review of recurring incident patterns
1. Incident Summary (Complete Within 24 Hours)
Incident ID: [AUTO-GENERATED] Date/Time: [Start] โ [End] (Duration: X hours) Severity: SEV-1 (revenue impact) | SEV-2 (customer impact) | SEV-3 (internal impact) Impact: [Users affected] | [Revenue lost] | [SLA breached Y/N] Detection: How was it found? (Monitoring / Customer report / Internal discovery) Detection Delay: Time from incident start โ first alert
2. Timeline (Minute-by-Minute for SEV-1, 15-min blocks for SEV-2/3)
HH:MM - Event description HH:MM - First alert triggered HH:MM - Team notified HH:MM - Investigation started HH:MM - Root cause identified HH:MM - Fix deployed HH:MM - Confirmed resolved
3. Root Cause Analysis โ 5 Whys
Why 1: [Direct cause] Why 2: [Why did that happen?] Why 3: [Why did THAT happen?] Why 4: [Systemic cause] Why 5: [Organizational/cultural root]
4. Contributing Factors
Score each factor 0-3 (0=not a factor, 3=primary contributor): FactorScoreNotesMissing/inadequate monitoringInsufficient testingDocumentation gapsProcess not followedKnowledge concentration (bus factor)Capacity/scaling limitsThird-party dependencyCommunication breakdownChange management failureTechnical debt
5. What Went Well
List 3-5 things that worked during the response: Fast detection? Good runbooks? Strong communication? Quick escalation?
6. Action Items
Every action MUST have an owner and deadline: #ActionOwnerDeadlinePriorityStatus1P0/P1/P2Open Priority definitions: P0: Must complete before next business day P1: Must complete within 1 week P2: Must complete within 1 sprint/month
7. Recurrence Prevention
Monitoring added/improved for this failure mode Runbook created/updated Test coverage added Architecture change needed? (If yes, create RFC) Training needed for team?
Blameless Post-Mortem Rules
Focus on systems, not individuals "What happened" not "who did it" Assume everyone acted with best intentions and available information The goal is learning, not punishment If you find yourself writing someone's name next to a mistake, rewrite it as a process gap
Incident Cost Calculator
Direct costs: Revenue lost during downtime: $___ SLA credits issued: $___ Emergency vendor/contractor costs: $___ Indirect costs: Engineering hours ร loaded rate: ___ hrs ร $___/hr = $___ Customer churn risk (affected users ร churn probability ร LTV): $___ Brand/reputation (estimate): $___ Total incident cost: $___ Cost per minute of downtime: $___
Quarterly Incident Review
Every quarter, analyze patterns across all post-mortems: Top 3 root cause categories โ Where should you invest in prevention? Mean time to detect (MTTD) โ Is monitoring improving? Mean time to resolve (MTTR) โ Is response getting faster? Action item completion rate โ Are you actually fixing things? Repeat incidents โ Same root cause twice = systemic failure Cost trend โ Total incident cost per quarter (should decrease)
Industry-Specific Post-Mortem Considerations
IndustryKey FocusRegulatory RequirementFintechTransaction integrity, audit trailSOX, PCI-DSS incident reportingHealthcarePHI exposure, patient safetyHIPAA breach notification (60 days)SaaSSLA compliance, data integritySOC 2 incident managementE-commerceOrder integrity, payment processingPCI-DSS, consumer protectionManufacturingSafety incidents, production lossOSHA reporting requirements
Go Deeper
Your post-mortems reveal where AI agents should be deployed first โ the repetitive failures, the manual monitoring gaps, the processes that break under load. Find your highest-cost gaps: AI Revenue Leak Calculator Industry-specific deployment playbooks: AfrexAI Context Packs โ $47 Pick 3: $97 | All 10: $197 | Everything: $247 Deploy your first agent: Agent Setup Wizard Built by AfrexAI โ turning incident patterns into automation opportunities.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- README.md