Search

PythonReactSEOPDF
OpenClaw

Afrexai Post Mortem

Post Mortem & Incident Review Framework

1kalin0 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install 1kalin/afrexai-post-mortem

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

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

Post-Mortem Template

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):

Factor Score Notes
Missing/inadequate monitoring
Insufficient testing
Documentation gaps
Process not followed
Knowledge concentration (bus factor)
Capacity/scaling limits
Third-party dependency
Communication breakdown
Change management failure
Technical 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:

| # | Actio...

Source information

Source
github
Repository
openclaw/skills
Path
skills/1kalin/afrexai-post-mortem
Version
—
Commit
1a3ef3689d4f3514b4138f41d6534486d20eac8b
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

README

Post-Mortem & Incident Review Framework

Structured, blameless post-mortems that prevent repeat failures. Includes 5-Whys root cause analysis, incident cost calculator, action tracking, and quarterly pattern review.

What's Inside

  • Complete post-mortem template (SEV-1 through SEV-3)
  • 5-Whys root cause analysis framework
  • 10-factor contributing cause scorecard
  • Incident cost calculator (direct + indirect)
  • Quarterly incident pattern review
  • Industry-specific regulatory requirements (HIPAA, SOX, PCI-DSS, SOC 2, OSHA)
  • Blameless culture guidelines

Who It's For

Engineering teams, SREs, ops leaders, and anyone who's tired of the same incidents repeating every quarter.

Usage

Install this skill and your AI agent will guide you through structured post-mortems, calculate incident costs, track action items, and surface recurring patterns.


Your incidents reveal where AI agents should deploy first.

Built by AfrexAI

Extracted content

SKILL.md
# 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

## Post-Mortem Template

### 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):

| Factor | Score | Notes |
|---|---|---|
| Missing/inadequate monitoring | | |
| Insufficient testing | | |
| Documentation gaps | | |
| Process not followed | | |
| Knowledge concentration (bus factor) | | |
| Capacity/scaling limits | | |
| Third-party dependency | | |
| Communication breakdown | | |
| Change management failure | | |
| Technical 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:

| # | Actio...
README
# Post-Mortem & Incident Review Framework

Structured, blameless post-mortems that prevent repeat failures. Includes 5-Whys root cause analysis, incident cost calculator, action tracking, and quarterly pattern review.

## What's Inside
- Complete post-mortem template (SEV-1 through SEV-3)
- 5-Whys root cause analysis framework
- 10-factor contributing cause scorecard
- Incident cost calculator (direct + indirect)
- Quarterly incident pattern review
- Industry-specific regulatory requirements (HIPAA, SOX, PCI-DSS, SOC 2, OSHA)
- Blameless culture guidelines

## Who It's For
Engineering teams, SREs, ops leaders, and anyone who's tired of the same incidents repeating every quarter.

## Usage
Install this skill and your AI agent will guide you through structured post-mortems, calculate incident costs, track action items, and surface recurring patterns.

---

**Your incidents reveal where AI agents should deploy first.**
- [AI Revenue Leak Calculator](https://afrexai-cto.github.io/ai-revenue-calculator/) — find your costliest gaps
- [Industry Context Packs — $47](https://afrexai-cto.github.io/context-packs/) — deployment playbooks for 10 verticals
- [Agent Setup Wizard](https://afrexai-cto.github.io/agent-setup/) — deploy your first agent

Built by [AfrexAI](https://afrexai-cto.github.io/context-packs/)

Related skills

OpenClaw

xint

0xnyk

X Intelligence CLI — search, monitor, analyze, and engage on X/Twitter. TypeScript + Bun. AI agent skill.

OpenClaw

bambu-studio-ai

heyixuan2

Bambu Lab 3D printer control and automation. Activate when user mentions: printer status, 3D printing, slice, analyze model, generate 3D, AMS filament, print monitor, Bambu Lab, or any 3D printing task. Full pi...

OpenClaw

flightclaw

jackculpan

Track flight prices from Google Flights with this OpenClaw skill. Search routes, monitor prices, and get alerts when prices drop.

OpenClaw

openclaw-trading-assistant

openclaw-trade

openclaw trading assistant| openclaw trading skill | nof1.ai & openclaw [moltbot] collaboration | We get the best practices from alpha arena trading seasons and bring it to clawdbot All top AI agents, realtime...