SkillAgentSearch skills...

nw-post-mortem-framework

Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning

Install / Use

npx skills add nWave-ai/nWave --skill nw-post-mortem-framework

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Supported Platforms

Universal

Tags

Our assessment of nw-post-mortem-framework

nw-post-mortem-framework scores 81/100 on our quality scale, 1010th of 1,156 Content & Media skills we index.

Its SKILL.md is 3.0 KB long, well organised into 24 sections with 1 code example: a solid amount of guidance for an agent.

It has 617 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
17/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so nw-post-mortem-framework is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-09. Automated pattern scan on 2026-10-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nw-post-mortem-framework compared with similar skills

All 4 of these similar skills score higher than nw-post-mortem-framework; compare them before choosing.

SkillScoreStarsUpdatedFormat
nw-post-mortem-framework (this skill)by nWave-ai816172mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install nw-post-mortem-framework?
Run npx skills add nWave-ai/nWave --skill nw-post-mortem-framework. The install tabs above show the steps for each supported agent.
Which AI agents does nw-post-mortem-framework work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is nw-post-mortem-framework safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nw-post-mortem-framework still maintained?
The repository was last updated about 2 months ago, so nw-post-mortem-framework is actively maintained.

name: nw-post-mortem-framework description: Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning user-invocable: false disable-model-invocation: true

Post-Mortem Framework

Principles

  • Blameless: focus on systems/processes, not individuals. People make reasonable decisions given available info.
  • Evidence-based: every finding backed by logs, metrics, or documented actions
  • Action-oriented: every finding produces concrete, assigned action item
  • Learning-focused: capture what worked alongside what failed

Post-Mortem Document Structure

# Post-Mortem: [Incident Title]

**Date**: [incident date]
**Duration**: [start to resolution]
**Severity**: [P0-P3]
**Author**: [analyst]

## Summary
[2-3 sentence overview: what happened, impact, resolution]

## Timeline
| Time | Event | Source |
|------|-------|--------|
| HH:MM | [event] | [log/metric/report] |

## Impact
- Users affected: [number/percentage]
- Duration of impact: [time]
- Business impact: [quantified if possible]
- Systems affected: [list]

## Root Cause Analysis
[5 Whys analysis with evidence at each level]

## Detection and Response
- Time to detect: [duration] -- [how detected]
- Time to respond: [duration] -- [first action]
- Time to mitigate: [duration] -- [mitigation applied]
- Time to resolve: [duration] -- [permanent fix]

## What Went Well
- [positive observations about detection, response, recovery]

## What Could Be Improved
- [areas where detection, response, recovery fell short]

## Action Items
| ID | Action | Owner | Priority | Due Date |
|----|--------|-------|----------|----------|
| 1 | [specific action] | [team/person] | [P0-P3] | [date] |

## Lessons Learned
- [key takeaways for the organization]

Incident Timeline Reconstruction

Sources

  1. Monitoring alerts/dashboards (timestamps) | 2. Deployment logs/CI-CD records
  2. Communication channels (Slack, email, incident) | 4. VCS (commits, merges, deploys) | 5. User reports/support tickets

Quality Checks

Events chronological with verified timestamps | gaps >5 min noted/explained | decision points identified with available info | causal relationships noted

Response Effectiveness Evaluation

Detection

Detected by monitoring or users? | Duration onset-to-detection? | Existing alerts relevant? Missing?

Escalation

Right team at right time? | Procedures followed? | Communication clear to stakeholders?

Resolution

Mitigation effective? | Rollback considered/viable? | Duration mitigation-to-permanent-fix?

Organizational Learning

Knowledge Capture

Document root causes as reusable patterns | update runbooks | share in retrospectives

Process Improvements

Update monitoring/alerting per detection gaps | revise deployment per rollback effectiveness | strengthen testing for failure scenario

Action Item Tracking

Every item has owner + due date | track in standups/sprint reviews | verify effectiveness post-deployment

Related Skills

View on GitHub
GitHub Stars617
CategoryContent
Updated2mo ago
Forks63

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions