Incident Postmortem

    3

    Transform raw incident logs and Slack threads into blameless, structured postmortems and 5-Whys RCA reports.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    2 usesSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    incident-postmortem

    Example session with this skill installed

    I need to write a postmortem for today's outage. It started with PR #402 at 14:02. PagerDuty alerted at 14:10, and we mitigated by diverting traffic to region B at 14:25. It was a DB timeout issue.

    • Read your context and instructions
    • Compiled the incident-postmortem

    Timeline
    14:02 Trigger - PR #402 deployed
    14:10 Detection - PagerDuty 'High Latency' alert
    14:25 Mitigation - Traffic diverted to region B
    5-Whys Root Cause: Missing CI check for DB connection timeouts.
    Action Item: Implement 'timeout-lint' in CI/CD pipeline. Owner: Platform Eng.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Write blameless, high-impact incident reports

    Transform chaotic production outages into structured engineering wisdom. This skill acts as a Senior SRE to help your team reconstruct timelines, identify systemic root causes, and define actionable improvements after any production incident, data loss event, or security breach.

    What it does

    • Reconstructs precise timelines: Consolidates raw data from Slack threads, PagerDuty alerts, logs, and metrics into a chronological event log.
    • Deep Root Cause Analysis: Employs the "5 Whys" method to move past technical triggers and uncover underlying process or architectural gaps.
    • Calculates Key Metrics: Automatically determines Time to Detect (TTD), Time to Mitigate (TTM), and total incident duration.
    • Generates Concrete Action Items: Creates P0-P2 tasks with owners and due dates, specifically designed to prevent recurrence and reduce blast radius.

    Why use this skill

    Writing postmortems is often a manual, time-consuming chore that engineers avoid. This skill automates the heavy lifting of data synthesis while maintaining a strictly blameless culture. Unlike generic AI prompting, it follows industry-standard frameworks from Google and PagerDuty, ensuring your reports are professional enough for leadership and detailed enough for dev teams.

    What the output looks like

    You receive a professional, markdown-ready postmortem document containing a summary for stakeholders, a detailed event-source timeline, a quantified impact analysis, and a prioritized table of action items focused on systemic fixes rather than human error.

    • Cannot directly access private Slack channels or logs without user copy-pasting text.
    • Accuracy depends on the level of detail provided in the raw input.
    • Does not automatically create Jira tickets.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    2 uses

    Times used to date

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 7 months ago

    Permissions

    No special permissions declared or detected

    Listed7 months ago

    What's inside

    Frequently Asked Questions

    The skill integrates seamlessly with popular SRE tools and AI agents that support Markdown or text-based inputs, such as AutoGPT, BabyAGI, and custom OpenAI-powered assistants. It is designed to work across any platform that can process unstructured data from Slack or PagerDuty.

    Simply provide the tool with your raw data—such as exported Slack conversation threads, PagerDuty log exports, or CloudWatch metric snapshots—and it will automatically synthesize them into a structured report. No manual data mapping is required to get started.

    While typical AI tools might suggest human error, this skill is specifically tuned to ignore blame and instead identify architectural weaknesses, missing monitoring alerts, and process bottlenecks as defined by industry-standard SRE principles.

    Purchasing this skill gives you the full logic set for generating postmortems and 5-Whys reports, a structured markdown template, and lifelong access to any future updates or refinements to the reporting logic.

    Yes, once the skill generates the initial timeline and analysis, you can easily add specific context, modify the '5 Whys' findings, or adjust the priority of action items directly within the generated Markdown document.

    New in Technical Documentation