Postmortem Draft logo

Postmortem Draft

Organization
runxhq
postmortem-draft

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.

Overview

Publisherrunxhq
Repositoryrunx
Skill namepostmortem-draft
Stars
105
Forks
109
Bundled files
6
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by runxhq on GitHub. Read the source before you install it.

Installation

Install the Postmortem Draft AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/runxhq/runx/tree/main/skills/postmortem-draft
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/runxhq/runx.git /tmp/runx
mkdir -p .claude/skills
cp -r /tmp/runx/skills/postmortem-draft .claude/skills/postmortem-draft
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Postmortem Draft in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Postmortem Draft on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Postmortem Draft is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Postmortem Draft

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

  1. Native data.digest binds the exact fragment set.
  2. The drafting agent assembles a summary, an evidence-cited timeline, a root cause with a status of known, suspected, or unknown, open unknowns, and owned action items.
  3. 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.
  4. The verdict separates completeness from honesty: a fully cited postmortem with a supported root cause and no open unknowns is publishable and carries a publish proposal gated on a human approver through message-send; a grounded but incomplete one seals needs_more_evidence and publishes nothing.

To build the fragment set from live systems, compose web-fetch or store reads upstream; the digest binds whatever evidence was supplied. Running the incident belongs to its operator; this skill explains it afterward.

Output

postmortem (runx/postmortem-draft.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_id and incident_fragments.

Agent task contracts

postmortem-draft-draft

Read incident_id 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Postmortem Draft AI skill do?

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.

Why use Postmortem Draft on TypingMind?

Because you install it once and use it with any model. Postmortem Draft is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Postmortem Draft in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/runxhq/runx/tree/main/skills/postmortem-draft. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Postmortem Draft?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Postmortem Draft?

As many as you like. As long as a model supports skills, you can use Postmortem Draft with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Postmortem Draft AI skill free?

Yes. It is published on GitHub by runxhq under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇