Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Content Creation
Incident Postmortem Framework
Generates structured blameless incident postmortems from raw notes, producing summaries, timelines, root cause analyses, impacts, action items, and preventio...
skill openclawclawhub Free
Generates structured blameless incident postmortems from raw notes, producing summaries, timelines, root cause analyses, impacts, action items, and preventio...
โฌ 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
Incident Postmortem Generator
Generate blameless incident postmortems from raw notes, Slack threads, or bullet points.
What It Does
Takes messy incident details and produces a structured postmortem document following Google/Atlassian SRE best practices.
Usage
Provide incident details in any format โ timeline bullets, Slack copy-paste, verbal notes โ and the agent will produce: Executive Summary โ What happened, impact, duration, severity Timeline โ Minute-by-minute from detection to resolution Root Cause Analysis โ 5 Whys format, no finger-pointing Impact Assessment โ Users affected, revenue impact, SLA breach Action Items โ Prioritized fixes with owners and deadlines Lessons Learned โ What worked, what didn't, what was lucky Prevention Measures โ Systemic changes to prevent recurrence
Instructions
When the user provides incident details: Ask clarifying questions ONLY if critical info is missing (severity, duration, or resolution are the minimum) Generate the full postmortem in markdown Flag any gaps the team should fill in before publishing Suggest 3-5 specific, actionable prevention measures ranked by effort/impact
Formatting Rules
Use ISO timestamps in timeline Bold severity level (SEV1-SEV4) Action items must have: description, owner placeholder, deadline placeholder, priority (P0-P3) Keep language blameless โ "the deploy process" not "Bob deployed"
Severity Guide
SEV1: Revenue-impacting, all users affected, >1hr SEV2: Major feature down, >30% users, >30min SEV3: Degraded performance, <30% users SEV4: Minor issue, workaround available
Example Input
prod went down at 2pm, bad deploy, rolled back at 2:45, ~500 users couldn't checkout, lost maybe $12k revenue
Example Output Structure
# Incident Postmortem: Checkout Service Outage **Date:** 2026-02-22 | **Severity:** SEV1 | **Duration:** 45 minutes **Author:** [Team Lead] | **Status:** Draft ## Executive Summary ...
Pro Tip
Run this after every incident, even small ones. The pattern recognition across postmortems is where the real value lives. Teams that write postmortems for SEV3+ incidents catch systemic issues 3x faster. Need help building incident response processes from scratch? Check out the AfrexAI Context Packs โ pre-built operational frameworks for SaaS, healthcare, legal, and 7 more industries. Starting at $47.
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- README.md