Menü
Post-mortem a context compaction — surface which main-thread tasks should have been subagents. Use when the user asks for /postmortem, or when reviewing why a session compacted.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Draft event copy in Mattie's voice — newsletter blurbs, Luma event descriptions and listings, invite copy, blast copy, forwardable event one-paragraphs. Use for anything an audience reads about an event we host, co-host, or lend the venue to. This is her EVENT register (image-first, receipt-backed, warm by invitation), NOT the sectioned executive-email register and NOT the casual burst voice.
Reply to an inbound Mission Robotics Tally submission — draft a from-Morrigan tour invite, send it via AgentMail with Mattie CC'd, and add/update the prospect in the Notion DB. Use when Mattie shares a Tally Forms notification (short tour-interest form Ek61oX or long intake kdkGYr) and wants the inbound handled.
Write a diary entry reflecting on the current session. Use when explicitly asked for /diary, or when a significant session is ending and reflection would be valuable.
Basierend auf der SOC-Berufsklassifikation
| name | postmortem |
| description | Post-mortem a context compaction — surface which main-thread tasks should have been subagents. Use when the user asks for /postmortem, or when reviewing why a session compacted. |
Post-mortem the most recent (or an older) context compaction. Surface which main-thread writes should have been dispatched to subagents.
Data source: ~/.claude/metrics/compactions.jsonl (written by the PreCompact hook). Each row references the transcript that led up to the compaction.
Dispatch-floor doctrine: any task that touches more than one file or produces more than 40 lines should be dispatched to a subagent. Compaction is the failure signal.
python3 ~/.claude/skills/postmortem/analyze.py
Optional integer arg: how many compactions back. 0 (default) = most recent. 1 = second-most-recent. Etc.
python3 ~/.claude/skills/postmortem/analyze.py 2 # three compactions ago
The script prints a JSON digest to stdout. If the metrics file is missing or empty, it prints a friendly message to stderr and exits 1 — report that to the user and stop.
The digest shape:
{
"compaction": { "ts": "...", "trigger": "auto|manual", "session_id": "...", "cwd": "..." },
"transcript": { "path": "...", "message_count": N },
"totals": {
"dispatches": 5,
"inline_writes": 12,
"inline_bash": 3,
"inline_bash_heavy": 1,
"inline_write_lines_est": 487
},
"inline_writes_over_floor": [ { "tool": "Write", "file_path": "...", "lines": 62 }, ... ],
"dispatches": [ { "description": "...", "subagent_type": "..." }, ... ]
}
150 words or less. Deliver the signal, stop.
Include:
foo.rs into a coder brief").Don't moralize. Don't explain the doctrine. Don't pad. Assume the reader knows what dispatching is — this is diagnostic output, not a lecture.
totals.dispatches is already high and inline_writes_over_floor is short, say so — "dispatch discipline was solid, the compaction came from volume not structure." Don't manufacture failure.