technical-postmortem SKILL.md skillA
technical-postmortem from webkubor/writing-standard-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add webkubor/writing-standard-skills/technical-postmortem@git:20261025.4eaa475Pins git:20261025.4eaa475 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- webkubor/writing-standard-skills
- Path
skills/technical-postmortem/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261025.4eaa475, committed Oct 25, 2026
- Size
- 8,965 bytes
- Repository stars
- 6
- License
- MIT
严肃技术故障复盘、事故通报（Postmortem）与对外公关的表达规范。基于防御性工程与无指责复盘（Blameless Postmortem）原则，剔除空洞道歉与甩锅推诿，下钻到机制防线与量化事实。触发："事故通报 / 写复盘 / postmortem / 线上故障复盘 / 宕机通报 / 故障原因分析 / 为什么挂了 / 事故报告"。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 严肃技术故障复盘与事故通报规范 事故复盘与故障通报不是“公关道歉信”，更不是“道德审判与甩锅大会”。**它的唯一目的是：用不可辩驳的客观事实还原真相，把根因锁定在系统机制与物理约束的缺失上，并给出一经部署就不可绕过的物理防复发措施。** 判断一份事故报告是否合格的唯一标准：**读完之后，用户和工程师是觉得“这家公司在遮遮掩掩推卸责任”，还是清楚地知道“系统在哪个物理环节断了、这次教训换来了什么永久防线”？** --- ## 零、事故通报六步骨架（The Postmortem Skeleton） 动笔撰写故障通报或技术复盘前，按此骨架填空，不缺步、不跳步： ``` ① 首屏摘要 故障定级 · 影响范围（受损比例/脏数据行数/时长） · 核心根因一句话 ② 时间线 UTC 时间戳驱动 · 状态变化 · 发现/止血/根治的客观动作（零修辞） ③ 根因下钻 5 Whys 机制下钻 · 归因于机制缺失，绝不下钻到“某员工疏忽” ④ 止血处置 当时采取的应急措施 · 恢复线上可用的临时绕行方案 ⑤ 永久防线 Action Items · 谁主责 · 何时上线 · 依赖的物理门禁/代码约束 ⑥ 外部证据 监控图表 · 日志指纹 · Git Commit SHA · 外部健康探测回执 ``` --- ## 一、🚫 事故通报四大禁忌（Anti-PR Blacklist） 任何准备发给用户、客户或管理层的事故通报，严禁出现以下“公关八股”： | 违规表述 | 为什么令人极其反感 | 工业级替代方案 | |---|---|---| | **“给您带来的不便敬请谅解”** | 万能无意义套话，用户受损时听到这话只觉冷漠与傲慢。 | 删掉！直接陈述补偿方案或已就绪的恢复动作（“受影响账单已全额回退，补偿配额已到账”）。 | | **“我们将深刻吸取教训，举一反三”** | 语言的巨人、行动的矮子。没有任何工程落点。 | 给出代码级约束（“代码已引入 pre-commit 语法门禁，同类配置错误将在提交时被直接拒绝”）。 | | **“由于某工程师操作不当 / 某同事失误”** | 把系统性漏洞甩给个人，暴露团队工程素养极差。 | 归因于防护机制缺失（“系统缺乏操作二次确认与沙箱隔离栅栏，允许未经验证的脚本直连了生产库”）。 | | **“极少数用户受到轻微影响”** | 掩耳盗铃、试图粉饰太平，被抓出真实数据直接信誉破产。 | 给出精确客观数字（“共影响 142 个并发请求（占同时段总流量的 0.18%），持续 14 分钟”）。 | --- ## 二、关键段落表达规范 ### 1. 影响面量化（Impact Scope） - **绝不使用模糊字眼**：禁止写“部分用户”、“短时间”、“个别接口”。 …
Read the whole file at its exact version.
How to install
mdr add webkubor/writing-standard-skills/technical-postmortem@sha256:82ee31da26f6613bThe line at the top of this page pins the label git:20261025.4eaa475, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_m7h7u35drf2537sg)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 25, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8965 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
webkubor/writing-standard-skills · 6 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m7h7u35drf2537sg GET https://markdownregistry.com/api/v1/resolve?ref=webkubor/writing-standard-skills/technical-postmortem GET https://markdownregistry.com/api/v1/blob/82ee31da26f6613b0b58efc1e5ab8dad00df9fb9a2d9810c5742993951c40a12
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.