postmortem

v1.2.0

Write a production-incident postmortem that reads well for humans and stays parseable by tooling: machine-read frontmatter, a numbered spine, and strict evidence rules

CodexClaude Code1 Skill

By Wagner Ignacio Pinto JuniorLicense: MIT0 GitHub starsUpdated 4 days ago

Directory evidence

Runtimes: Codex and Claude Code
Parsed components: 1 skill or MCP entry
Source updated: Sep 19, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install postmortem for Codex and Claude Code

Installs for the current user

codex plugin marketplace add wagneripjr/skills
codex plugin marketplace upgrade wagner-skills-marketplace
codex plugin add postmortem@wagner-skills-marketplace

Paste and run these commands in a terminal with Codex. They add and refresh the wagner-skills-marketplace catalog, then install this plugin.

Compatibility: the page URL and API slug “postmortem” remain stable.

Codex: postmortem@agent-plugin-marketplace → postmortem@wagner-skills-marketplace

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/wagneripjr/skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/postmortem/.

Plugin files

plugins/postmortem/

├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
└── skills/postmortem/SKILL.md

Included Skills1

postmortemskills/postmortem/SKILL.md

Write a production-incident postmortem that reads well for humans and stays parseable by tooling. Produces docs/postmortems/YYYY-MM-DD-<slug>.md with machine-read YAML frontmatter (severity critical|high|medium|low), a stable H1 + filename date that together form a finding-id, and a numbered spine — executive summary, impact/blast radius with per-service evidence, timeline, root cause (mechanism + 5 whys + discarded hypotheses), empirical proof, detection, remediation (palliative vs root fix), action items, lessons learned, read-only appendices. Triggers: 'write a postmortem', 'post-incident review', 'incident record', 'document this outage', 'RCA document', or right after resolving/mitigating any production incident. NOT for reconciling a postmortem with the decision it contradicted. NOT for bug reports. NOT for live incident response.

Plugin manifests2

plugins/postmortem/.codex-plugin/plugin.json

{
  "name": "postmortem",
  "description": "Write a production-incident postmortem that reads well for humans and stays parseable by tooling: machine-read frontmatter, a numbered spine, and strict evidence rules",
  "version": "1.2.0",
  "author": {
    "name": "Wagner Ignacio Pinto Junior",
    "email": "[email protected]"
  },
  "repository": "https://github.com/wagneripjr/skills",
  "homepage": "https://github.com/wagneripjr/skills",
  "license": "MIT",
  "keywords": [
    "postmortem",
    "incident-response",
    "sre"
  ],
  "skills": [
    "./skills/postmortem"
  ]
}

plugins/postmortem/.claude-plugin/plugin.json

{
  "name": "postmortem",
  "description": "Write a production-incident postmortem that reads well for humans and stays parseable by tooling: machine-read frontmatter, a numbered spine, and strict evidence rules",
  "version": "1.2.0",
  "author": {
    "name": "Wagner Ignacio Pinto Junior",
    "email": "[email protected]"
  },
  "repository": "https://github.com/wagneripjr/skills",
  "homepage": "https://github.com/wagneripjr/skills",
  "license": "MIT",
  "keywords": [
    "postmortem",
    "incident-response",
    "sre"
  ]
}

Browse the “postmortem” tag →

misakanet

by Ikalus1988

Failure-memory network for AI coding agents: search evidence-rated failure lessons, submit new failures, and turn crashes into reusable knowledge.

Codex

492Updated last week

observability-sre

by Matt Corbett

Observability & SRE team — agents (observability-engineer, sre-reliability-engineer, incident-commander) for making a system observable and keeping it reliable: instrumentation on OpenTelemetry (metrics/logs/traces, semantic conventions, sampling, cardinality control), SLI/SLO and error-budget design, symptom-based alerting (multi-window burn-rate, alert on user pain not causes), incident response (severity, roles, comms, blameless postmortems, action-item follow-through), and proactive resilience verification via chaos engineering (steady-state hypotheses, blast-radius-limited fault injection, game days). skills, a decision-tree knowledge bank (alert-design + SLO-target trees + a chaos-engineering reference + a dated 2026 tooling map), best-practices, templates, commands, an advisory hook. Seams: deploy health-gates -> devops-cicd, cluster telemetry -> cloud-native-kubernetes, API SLOs -> api-engineering, cloud-native monitors -> azure/aws/gcp-cloud. Requires ravenclaude-core@>=0.7.0.

Claude Code7 Skills

7Updated last week

humanize

by XRenSiu

Humanize — make AI-written technical prose read like a competent human professional wrote it, at the level where readers actually get lost: discourse, not vocabulary. Three skills. `/humanize` rewrites a draft (zh/en) without changing a single fact: it targets the mechanisms behind 'every word is clear but I can't follow' — given-new inversion, broken topic strings, stress-position leakage (participle / 以实现… tails), lists replacing argument, cross-section restatement, stance flattening, generic openings, summary closers — plus the solved lexical/syntax/format layer (Wikipedia 'Signs of AI writing' + 2026 density-era tics: mannered prose, invented jargon, 'not X, it's Y') and Chinese translationese (yage.ai four classes + 余光中欧化 catalog, CCL-2023 corpus-backed). Three non-skippable gates: humanlint.py (23 surface metrics, zh/en, 0-100 AI-flavor index, calibrated on four fixtures: AI 60/63 vs human 2/0), factdiff.py (numbers / dates / identifiers / URLs / paths zero add-or-drop, plus certainty-drift warning per Belem 2026), and a context-isolated cold-reader agent that records per paragraph where a reader who never saw the brief loses the thread (expected / got / lost_at / told_not_shown) — never self-graded in the drafting context (self-refine amplifies self-bias); verify_coldread.py recomputes the reader's verdict from its five declared rules and enforces the 2-round cap mechanically (v0.2.0). Max 2 revision rounds, then deliver with the residual named. Genre decides whether structure may move (v0.3.0): proposal / design / adr / memo may be reorganised; report / readme / reference run with --keep-structure, where structdiff.py rejects any change to the heading-level sequence, list blocks and item counts, table shapes or code blocks — only the sentences inside prose paragraphs change; humanlint gained a matching `report` threshold tier. `/techdoc` writes a proposal / design doc / ADR / postmortem / memo from a brief in the shape senior engineers use (Google design docs, Oxide RFD, Amazon 6-pager, Nygard ADR, Shape Up, HashiCorp/Rust RFC, 阿里安全生产): triggering incident with a number first, decision in one sentence, obvious alternatives killed with specific reasons, all consequences, rollout/rollback, open questions last — enforced as product order by verify_techdoc.py; facts only from brief/materials/domain knowledge, else [需核实]. `/voice-profile` distills the user's own 3–5 samples into an executable .humanize/voice.md (rhythm stats from humanlint, quoted sentence habits, personal 忌口表 with replacements, positive examples for completion-style few-shot — the technique with 20x measured style-match gain), gated by verify_voice.py. Ships rules/human-voice.md as an always-on contract pasteable into CLAUDE.md. Explicitly NOT for beating AI detectors (they train on humanizer output), NOT for injecting slang/emoji/typos as 'texture' (a new tell in technical register). All static_only tier: scripts smoke-tested on fixtures; behavioral delta on held-out drafts unverified.

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[postmortem on Agent Plugins Marketplace](https://pluginsmp.com/plugins/postmortem)