recipe-post-mortem-setup

recipe-post-mortem-setup is a skill for Claude Code from fakoli/fakoli-plugins. It costs 28 tokens per session (485 once invoked), scanned A, original, MIT.

An incident follow-up workflow that creates a structured post-mortem document, schedules a review meeting, and notifies the team in Google Chat.

In plain words
What is it for?
Use it after an incident to record the summary, timeline, root cause, impact, action items, and lessons learned, then arrange a team review.
Why use it?
It brings the main follow-up tasks after an incident into one process instead of handling the document, meeting, and announcement separately.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the gws plugin — 94 skills, 15 commands, 11 agents shipped together

Good fit Use it after an incident to record the summary, timeline, root cause, impact, action items, and lessons learned, then arrange a team review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fakoli/fakoli-plugins/recipe-post-mortem-setup
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fakoli/fakoli-plugins --skill recipe-post-mortem-setup
Clone the repo
git clone --depth 1 https://github.com/fakoli/fakoli-plugins

Made for: Claude Code.

Or install gws, the plugin that ships this one along with the rest of its 94 skills, 15 commands, 11 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for recipe-post-mortem-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup/github.svg)](https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup)
Your own site
<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for recipe-post-mortem-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-post-mortem-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 485 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00485
Opus 5.5 $0.00011 $0.00194
Sonnet 5.5 $0.00006 $0.00097
Haiku 4.5 $0.00003 $0.00049

Measured 1mo ago against content hash c3e2c14bd3f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

recipe-post-mortem-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/gws/skills/recipe-post-mortem-setup/SKILL.md · 72 lines

What it actually says

Set Up Post-Mortem

Create a post-mortem document, schedule a review meeting, and notify the team — all in one workflow.

When to Use

Use this workflow after an incident when the user needs to set up the post-mortem process: create a structured document, schedule a review meeting, and notify the team.

Workflow

1. Gather incident details

Ask the user for:

  • Incident name (e.g., "API Outage 2026-03-14")
  • Team/attendees for the review meeting
  • Preferred review time
  • Chat space for the notification

2. Create the post-mortem document

gws docs +write \
  --title 'Post-Mortem: INCIDENT_NAME' \
  --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Impact\n\n## Action Items\n\n## Lessons Learned'

Capture the document ID.

3. Schedule the review meeting

gws calendar +insert \
  --summary 'Post-Mortem Review: INCIDENT_NAME' \
  --attendee [email protected] \
  --start 'REVIEW_TIME' \
  --end 'REVIEW_END_TIME' \
  --dry-run

Confirm, then execute.

4. Notify the team in Chat

gws chat +send \
  --space spaces/SPACE_ID \
  --text 'Post-mortem scheduled for INCIDENT_NAME. Doc: DOC_LINK | Review: MEETING_TIME'

5. Share the document

gws drive permissions create \
  --params '{"fileId": "DOC_ID"}' \
  --json '{"role": "writer", "type": "user", "emailAddress": "[email protected]"}'

Safety

  • Use --dry-run on the calendar event and chat message before executing
  • Confirm the attendee list and chat space with the user

Tips

  • Share the doc with writer access so the team can contribute
  • Include the doc link in the calendar event description
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 72 lines · 28 tokens per session scan A c3e2c14bd3f1

Subscribe to this mod's changes

recipe-post-mortem-setup is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 485 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

issue-triage

Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…

Marcel-Bich/marcel-bich-claude-marketplace · 97 tokens

requirements-verbatim

Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…

Marcel-Bich/marcel-bich-claude-marketplace · 101 tokens

notion-integration

Integrate with Notion — database queries, page creation, property updates, and content sync.

inbharatai/claude-skills · 24 tokens

work-planning

Design the complete work hierarchy for a Paperclip company — Goals, Projects, and Tasks as a unified top-down planning workflow. Produces .planning.json for deterministic generation of goals/, projects/, and tasks/ directories. Use when creating a new company's work plan, reorganizing work structure, or linking goals…

lukaskellerstein/claude-my-marketplace · 70 tokens

docx

This skill should be activated when the user asks to create a Word document, report, memo, letter, proposal, whitepaper, or anything involving .docx output. Also triggers when the user says 'write a report', 'create a document', 'make a Word file', 'draft a proposal', 'generate a whitepaper', or mentions .docx.…

lukaskellerstein/claude-my-marketplace · 131 tokens

xlsx

This skill should be activated when the user asks to create, edit, read, or analyze Excel spreadsheet files (.xlsx, .xlsm, .csv, .tsv). Triggers for: building financial models, creating data tables, formatting spreadsheets, adding formulas, cleaning tabular data, converting between tabular formats. Also triggers when…

lukaskellerstein/claude-my-marketplace · 106 tokens