Token导航 LogoToken导航TokenDH.com
运维需要联网clawhub未标认证来源可访问clear审计通过

afrexai-postmortem阿弗莱克赛尸检

Agent Skill

afrexai-postmortem 用于补充运维相关能力,适合在 OpenClaw 中需要让 Agent 承接运维相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

15,324

周安装

626

GitHub Stars

公开资料未说明

下载量

4,908
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:afrexai-postmortem(阿弗莱克赛尸检)
来源仓库:https://github.com/1kalin/afrexai-postmortem
安装命令:
openclaw skills install afrexai-postmortem
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install afrexai-postmortem

简介

afrexai-postmortem 根据事件记录生成结构化无可指责的事后分析报告。

  • 适用于技术团队复盘故障、提取教训并制定预防措施。
  • 输出包括时间线、根本原因、影响范围与行动项目列表。
  • 使用时需确保原始日志完整、时间戳准确且无主观偏见。
  • 涉及用户影响时应同步通知相关方并提供补偿或解释方案。

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

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

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

75.7%
按下载量换算3,715

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills