incident-postmortem SKILL.md skillA
incident-postmortem from kimyx0207/kim_service is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kimyx0207/kim_service/incident-postmortem@git:20261113.3967162Pins git:20261113.3967162 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kimyx0207/kim_service
- Path
skills/incident-postmortem/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261113.3967162, committed Nov 13, 2026
- Size
- 2,918 bytes
- Repository stars
- 193
- License
- MIT
整理客户影响、故障时间线、系统促因和可验证改进行动 incident postmortem action validation reliability.
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
# 故障复盘与行动验证 把事故记录变成能复核的影响与恢复时间线,并让每一项改进都有负责人、期限和完成证据,减少“加强意识”式空泛结论。 ## 使用 读取[专业方法](references/professional-method.md)与[交付模板](references/delivery-template.md),按 `method.json` 顺序处理实际材料。 ```sh node skills/incident-postmortem/scripts/run.mjs --input-json - < skills/incident-postmortem/examples/input.json ``` 该示例是合成数据。替换输入时保持单位、身份和版本一致。脚本从 stdin 读取 JSON,stdout 返回一个带输入/规则哈希的回执;没有网络、付费模型调用或业务写入。脚本输出需配合领域说明,不能当成全部专业判断。完整机器结构见 `capability.json`,示例期望和反例见[案例](evals/professional-cases.json)。 ## 工作顺序 1. 从监控、请求日志、变更单和应急记录建立统一时区时间线;区分用户影响、检测、缓解和真正恢复。 2. 运行helper重算四段时长,人工核对日志定位与客户影响分母;时序矛盾先回源修正。 3. 按触发因素、系统促因、检测缺口、恢复障碍写因果假设,给支持及反证,不按事件相邻直接定因。 4. 将行动分为prevent/detect/mitigate,写负责人、期限和可观察完成条件,再检查逾期和虚假关闭。 5. 交复盘正文、行动验证表及未核结论;实际通知、生产变更与关单交调用方。 ## 交付与判断 时间按显式时区比较且开始≤发现≤缓解≤恢复≤观察时点;客户影响时长与分段相加一致。每项完成状态需要证据引用,缺失类型与逾期不能被平均分抵消。 缺行动类型、负责人/期限/验证条件、逾期未完成或声称完成却无证据时needs_review;completed只表示给定记录检查完成且没有这些缺口。 ## 范围 - 本包不替代正在发生的应急指挥,不自动隔离或重启生产系统。 - 单次事件时间不能当成平均MTTR,不按人员责备代替系统分析。 - 不把填完行动表等同完成改进,不自动发送事故通报。 公开事故通报、生产变更或责任处置沿用现有事故负责人授权;复盘编写和时间复算直接推进。 普通可逆的读取、复算与草稿编制直接按当前任务授权推进。`needs_probe` 表示宿主未认证,不意味着本地脚本不可运行。包保留完整目录即可独立运行;复制入口一份不会携带资料。 ## 来源 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lhfrhk2cwqx6kyll/e2515f7651d3cb4a95f4a98dda62d46eaba28813a66ffa5707056755a15f0266.json
Then /plugin install incident-postmortem@markdownregistry-lhfrhk2cwqx6kyll in Claude Code. It installs git:20261113.3967162, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kimyx0207/kim_service/incident-postmortem@sha256:e2515f7651d3cb4aThe line at the top of this page pins the label git:20261113.3967162, 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_lhfrhk2cwqx6kyll)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kimyx0207/kim_service/incident-postmortem since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of incident-postmortem from somewhere else? Ask it: where did my incident-postmortem come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 13, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/incident-postmortem/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (2918 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
kimyx0207/kim_service · 193 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lhfrhk2cwqx6kyll GET https://markdownregistry.com/api/v1/resolve?ref=kimyx0207/kim_service/incident-postmortem GET https://markdownregistry.com/api/v1/blob/e2515f7651d3cb4a95f4a98dda62d46eaba28813a66ffa5707056755a15f0266
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.
More from kimyx0207/kim_service
Every file in kimyx0207/kim_service