postmortem

Name: postmortem
Author: neurofoo

github.com/neurofooCloud & DevOps123105 installsUpdated 41w ago

About postmortem

postmortem is a structured skill for teams analyzing incidents without assigning blame. It guides a review from impact and timeline through causes, lessons, and owned action items.

Key features

01Blameless incident analysis
02Executive summary and timeline
03Impact and root cause review
04Action items with owners
05Lessons learned section

Use cases

01Documenting a service incident
02Reviewing detection and mitigation delays
03Assigning follow-up prevention work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/neurofoo/agent-skills --skill postmortem

After installing, type/postmortemin Claude Code to confirm it loaded.

Details

From the project README

Blameless Post-Mortem

Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.

Instructions

Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.

Output Format

Executive Summary

Incident: [One-line description] Date/Time: [When it occurred] Duration: [How long] Severity: [Critical/High/Medium/Low]

Summary [2-3 sentence overview: what happened, impact, resolution]

Timeline

All times in [timezone].

Time	Event	Actor
HH:MM	[What happened]	[Who/what did it]
HH:MM	[Detection]	[How it was noticed]
HH:MM	[Response action]	[Who responded]
HH:MM	[Resolution]	[What fixed it]

Key Moments

Trigger: [What initiated the incident]
Detection: [How/when we knew something was wrong]
Mitigation: [When bleeding was stopped]
Resolution: [When fully resolved]

Impact

Customer Impact

Users affected: [number]
Duration of impact: [time]
Symptoms experienced: [what users saw]

Business Impact

Revenue impact: [if applicable]
SLA/SLO breach: [yes/no, details]

Root Cause Analysis

Root Cause [The fundamental reason this happened—not the trigger, but why the trigger caused an incident]

Trigger [The immediate cause—what set things in motion]

Contributing Factors

Factor	How It Contributed
[factor]	[explanation]

Why Wasn't This Caught?

Why didn't tests catch it?
Why didn't monitoring alert earlier?

What Went Well

What Worked	Why It Helped
[thing]	[explanation]

What Went Poorly

What Failed	Impact
[thing]	[impact]

Action Items

Immediate (This week)

Action	Owner	Due
[action]	[owner]	[date]

Short-term (This month)

Action	Owner	Due
[action]	[owner]	[date]

Lessons Learned

[lesson]
[lesson]
[lesson]

Guidelines

Blameless: "The deploy script didn't validate" not "Alice deployed without checking"
Thorough timeline: Include everything, even embarrassing delays
Specific actions: "Add memory alerting" not "Improve monitoring"
Assigned owners: Unowned actions don't happen

$ARGUMENTS

Comments

Markdown supported

Details

Author: neurofoo
Repository: neurofoo/agent-skills
Category: Cloud & DevOps
Installs: 105
GitHub stars: 123

Report

More skills

All skills

lark-apps

open.feishu.cn

743.6k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

wizard

github.com/mattpocock

580.6k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-prepare

github.com/microsoft

574.6k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

azure-ai

github.com/microsoft

573.9k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.