技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 343 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：1kalin/afrexai-postmortem
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
The skill is an instruction-only postmortem generator whose requirements and instructions are consistent with its stated purpose and do not request extra credentials or installs.
目的
Name, description, and runtime instructions align: the skill transforms incident notes into structured postmortems and does not request unrelated binaries, credentials, or config paths.
说明范围
SKILL.md contains only stepwise guidance for producing postmortems (ask clarifying questions, generate markdown, flag gaps, suggest prevention measures). It does not instruct reading system files, environment variables, or sending data to external endpoints beyond an informational link.
安装机制
No install spec and no code files — instruction-only skill. This is the lowest-risk install profile (nothing is written to disk by the skill itself).
证书
The skill declares no required environment variables, credentials, or config paths. Nothing requested is disproportionate to creating written postmortems.
持久
always is false and the skill does not request permanent presence or elevated system privileges. Autonomous invocation is allowed by default for skills on the platform, but this skill doesn't combine that with any high-risk access.
综合结论
This skill appears coherent and only provides instructions for formatting incident postmortems. Before using it, avoid pasting sensitive data (secrets, full logs with tokens, or personal data) into the prompt because anything you provide will be used to generate the document. Verify severity/duration fields and any numeric estimates (revenue impact, affected users) — the model may hallucinate or round figures. Review action-item owners and dea…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Incident Postmortem Framework」。简介：Generates structured blameless incident postmortems from raw notes, producing s…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/1kalin/afrexai-postmortem/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
# 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:
1. **Executive Summary** — What happened, impact, duration, severity
2. **Timeline** — Minute-by-minute from detection to resolution
3. **Root Cause Analysis** — 5 Whys format, no finger-pointing
4. **Impact Assessment** — Users affected, revenue impact, SLA breach
5. **Action Items** — Prioritized fixes with owners and deadlines
6. **Lessons Learned** — What worked, what didn't, what was lucky
7. **Prevention Measures** — Systemic changes to prevent recurrence
## Instructions
When the user provides incident details:
1. Ask clarifying questions ONLY if critical info is missing (severity, duration, or resolution are the minimum)
2. Generate the full postmortem in markdown
3. Flag any gaps the team should fill in before publishing
4. 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
```markdown
# 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](https://afrexai-cto.github.io/context-packs/) — pre-built operational frameworks for SaaS, healthcare, legal, and 7 more industries. Starting at $47.