POSTMORTEM
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill postmortem --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Postmortem?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-postmortem)More formats (shields.io, HTML) on the badges page.
---
name: postmortem
description: |
POSTMORTEM
---
---
description: Create blameless postmortem from the incident we just resolved
argument-hint: [optional: additional context or specific focus]
---
# POSTMORTEM
Generate a blameless postmortem from this conversation.
You just helped resolve an incident. The investigation context, hypotheses, evidence, and fix are all in this conversation (and likely in an INCIDENT.md file).
## Output Structure
Write a postmortem with:
- **Summary**: One paragraph - what happened, impact, resolution
- **Timeline**: Key events in UTC (use conversation timestamps if available)
- **Root Cause**: The actual underlying cause (not symptoms)
- **5 Whys**: Dig to systemic factors
- **What Went Well**: Recognition of good practices during response
- **What Went Wrong**: Honest assessment without blame
- **Follow-up Actions**: Concrete items with clear ownership
## Philosophy
- **Blameless**: Focus on systems, processes, and tools - not people
- **Honest**: Don't minimize or exaggerate
- **Actionable**: Every lesson should have a concrete follow-up
If INCIDENT.md exists, update its postmortem section. Otherwise create POSTMORTEM-{timestamp}.md.
Optional focus: **$ARGUMENTS**
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.