postmortem-maker
Skill97 starsChanged 32 days agoApache-2.0View on GitHub
Turn resolved-incident fragments into a traceable postmortem that separates fragment-cited facts from hypotheses, blocks publication while unknowns remain, and keeps the comms send behind a human gate.
In this repository94 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- runxSkill
- adopt-skillSkill
- agencySkill
- answer-from-docsSkill
- attention-reviewSkill
- audit-receiptSkill
- brand-voiceSkill
- business-opsSkill
- chargeSkill
- chief-of-staffSkill
- cold-outreachSkill
- content-pipelineSkill
- contract-drafterSkill
- conversation-replySkill
- conversation-reviewSkill
- crm-cleanupSkill
- cve-auditSkill
- data-storeSkill
- data-subject-requestSkill
- deep-researchSkill
- diagnose-skill-runSkill
- dispute-respondSkill
- ecosystem-briefSkill
- extractSkill
- ghostwriteSkill
- github-pr-commentSkill
- github-pr-reviewSkill
- github-syncSkill
- google-analyticsSkill
- google-calendarSkill
- google-search-consoleSkill
- governed-outboundSkill
- helpdeskSkill
- incident-commanderSkill
- issue-intakeSkill
- issue-to-prSkill
- issue-triageSkill
- knowledge-routerSkill
- lead-enrichmentSkill
- lead-qualifySkill
- least-privilegeSkill
- ledgerSkill
- list-hygiene-judgeSkill
- marketplace-invokeSkill
- meeting-followupSkill
- mock-chargeSkill
- mock-paySkill
- mock-refundSkill
- moltbookSkill
- n8n-handoffSkill
- nitrosendSkill
- nws-weather-forecastSkill
- open-meteo-weather-forecastSkill
- operator-inboxSkill
- ops-deskSkill
- organic-growthSkill
- policy-authorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
Read incident_ref and incident_fragments from step inputs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Postmortem Maker
Produce a postmortem that never pretends unknowns are facts. The supplied incident fragments are the only evidence; the drafting agent separates what happened from what is suspected, and deterministic code verifies every claimed fact against the fragments. Publication is a gated proposal, never an effect of this skill.
Procedure
- Native
data.digestbinds the exact fragment set. - The drafting agent assembles a summary, an evidence-cited timeline, a root
cause with a status of
known,suspected, orunknown, open unknowns, and owned action items. - Deterministic enforcement checks every timeline entry and any non-unknown root cause: the cited fragment must exist and the quote must appear verbatim in that fragment's text. An invented citation refuses the whole run. Action items must carry an action and an owner.
- The verdict separates completeness from honesty: a fully cited postmortem
with a supported root cause and no open unknowns is
publishableand carries a publish proposal gated on a human approver throughsend-as; a grounded but incomplete one sealsneeds_more_evidenceand publishes nothing.
To build the fragment set from live systems, compose web-fetch or
data-store reads upstream; the digest binds whatever evidence was supplied.
incident-commander owns running the incident; this skill owns explaining it
afterward.
Output
postmortem (runx.postmortem.v1) carries decision (publishable,
needs_more_evidence, refused), summary, the cited timeline,
root_cause, unknowns, action_items, the gated publish_proposal or
null, validation, and the fragments digest. publish_performed is always
false.
Inputs are incident_ref and incident_fragments.
Agent task contracts
postmortem-maker-draft
Read incident_ref and incident_fragments from step inputs. Return
postmortem_draft with summary, timeline entries (each entry,
fragment_id, quote), root_cause (status, and for known or suspected a
statement, fragment_id, and quote), unknowns, and action_items
(each action, owner). Quote fragments verbatim, mark anything the
fragments do not support as unknown rather than asserting it, and never
invent fragments, quotes, owners, or deadlines.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

