loading
loading
Write a blameless postmortem with a timeline, root causes, and corrective actions that can be verified.
Blameless by design, and every corrective action gets an owner, a date, and a way to verify it — so the postmortem actually changes something.
Listed for review
No verified public repo for this skill yet, so this page does not give you an install command. Skills with a verified source install in one command — or fully manual: copy the skill folder into .claude/skills/ and your agent picks it up.
Boostor Quality Score
84/100 · B
Incident Postmortem Writer takes an incident timeline, logs, customer impact, and mitigation notes, then writes a blameless postmortem: timeline, impact, root causes, contributing factors, and corrective actions. It pushes past the proximate cause to the contributing factors, and it gives every corrective action an owner, a due date, and a verification method — so the document drives change instead of becoming a blamey, action-free write-up nobody revisits.
Score a batch of ad variants on angle, clarity, proof, and risk — and suggest distinct next angles.
Stops a batch of ad variants from being ten takes on one weak angle — scores each on proof and risk, then pushes distinct next angles.
Transparent + deterministic: every point above is computed from this skill's real fields plus a prompt-injection safety scan. No black box, no pay-to-rank.
Pull AI copy back to brand voice, flag banned phrases, and mark any claim that still needs proof.
Fixes voice without flattening you into generic SaaS copy — it preserves the specifics and flags the claims that still need proof.
Generate human-readable changelogs from git history and PR descriptions.
Turns git log into a changelog a human would actually read, grouped by feature, fix, and breaking change — the release chore most teams skip until launch day.