More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Incident Postmortem Studio Pro

    1

    Create evidence-linked incident reviews, editable timelines and assessment maps, with verified corrective-action follow-through.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Incident Postmortem Studio Pro

    Incident Postmortem Studio Pro

    Example session with this skill installed

    Review the fictional Tenant routing interruption study. Preserve all three source files, distinguish the disputed early recovery message from reviewed scope validation, show the evidence-linked timeline and assessment map, and create editable report/chart snapshots plus an owner-led corrective-action tracker.

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

    Tenant routing interruption — fictional demonstration
    3 original sources, 12 exact evidence excerpts, 7 events retained.
    Impact start: 2026-10-20T09:00:00Z. Detection: 09:03:00Z. Mitigation: 09:20:00Z. Reviewed recovery: 09:45:00Z.
    Single-incident intervals: impact to detection 3 minutes; detection to mitigation 17 minutes; impact to reviewed recovery 45 minutes. The early 09:36 recovery message remains disputed and is not used as the recovery endpoint.
    Observed impact: 120 failed checks of 1200 synthetic transaction checks in the supplied fixed window. This is not a unique-customer or financial-impact count.
    Assessment: isolated replay supports the routing mechanism in its tested scope. One control-gap relationship remains hypothetical; the helper does not declare a universal root cause.
    Action A1: gate tenant routing against shard health. Owner: Routing owner; priority high; control prevent; due 2026-10-24; in progress and overdue as of 2026-10-26. Acceptance: affected-path canary fails against the unavailable shard and passes after safe routing. Verification evidence/reviewer not yet supplied; not verified.
    Generated work: self-contained HTML, editable SVG timeline/map, CSV registers, private source/project/evidence/history and hashes; optional native DOCX/PPTX and six-sheet XLSX when host dependencies are available. Rebuild after changing the source. Share views need access/editorial review.

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

    About this skill

    Turn incident records into an evidence-linked review your team can inspect, edit and follow through.

    Incident Postmortem Studio Pro helps a capable agent reconstruct supplied incident records, retain uncertainty, assess explanations against evidence and prepare practical corrective-action follow-up. It works in English. It is a post-incident review workflow, not a production responder or an automatic root-cause detector.

    A useful review, not just a polished template

    Keep original UTF-8 source bytes, names and SHA256 hashes; link exact excerpts to stable event, assessment and action IDs. Preserve original timestamp literals and explicit offsets while ordering events in UTC. Choose metric endpoints deliberately: impact start to detection, detection to mitigation, and impact start to reviewed recovery. These are single-incident intervals, not mean-time metrics. Missing or unverified endpoints remain unavailable. Merge overlapping intervals only within the same named scope; do not invent affected-user counts or financial impact.

    Separate observed mechanisms, changes, control gaps, hypotheses, counter evidence and unresolved explanations. A supported node does not prove its outgoing relationship; reviewed causal relationships need their own evidence and supported endpoints. Timing alone is not causation. Structural validation checks references and reviewer attestations, not source authenticity or semantic truth.

    24 contexts and 96 complete fictional studies

    Cover SaaS availability; API performance; databases; deployment/rollback; configuration/flags; DNS/certificates; dependencies; data pipelines; authentication; AI/agent workflows; checkout integrations; backup/restore; mobile offline sync; CDN/cache; container scheduling; storage/capacity; queues/events; monitoring/paging; batch/file delivery; webhooks; multi-region failover; security containment review; internal workflow automation; and research computing/HPC.

    Each context has different trigger, mechanism and control-gap records, plus tailored controls and testable acceptance criteria. Four evidence-workflow variants per context cover reviewed replay, overlapping intervals, conflicting evidence and unresolved milestones. These are 96 original synthetic exercises, not 96 independent investigation methods or real customer incidents. Security and research examples do not establish a breach, regulatory compliance or scientific-result validity.

    Edit the review without losing the source

    An optional loopback workbench supports clean source import, exact excerpt selection, searchable evidence/reference pickers, guided event/assessment/link/action/narrative editing, event and excerpt search, draggable native diagrams and keyboard node movement. Use focus mode, undo/redo and project save/reopen. Unrelated accepted revisions preserve unsaved form drafts; apply each form before saving the accepted project. Deleting a referenced record is blocked and lists its dependents. Complex impact scopes/measures remain in the project/agent workflow. First user-source import from a fictional study clears fictional events, narrative and history.

    Three actual HTML layouts—journal, command and briefing—combine with twelve visual foundations and internal/executive/customer reader views. Add a summary, what worked, what hindered response and learning notes. Draft narrative remains clearly marked and is excluded from customer views. Customer mode is an editorial filter, not anonymization or proof of certainty.

    Follow-through with evidence

    Set owners, due dates, priority and prevention/detection/mitigation/recovery/communication categories. Track HTTPS issue references and next-review notes; filter and sort actions by priority, owner and due date. A tracking reference does not create, fetch or synchronize a remote ticket. Reported done is separate from verified: verified closure requires an owner, acceptance criteria, verification evidence, named reviewer and actual review. Overdue uses the explicit review-as-of date. Review-next prompts expose gaps, not an approval score. Editable history records before/after values and source hashes; it is not tamper-proof attestation.

    Genuinely editable generated work

    The standard-library core creates self-contained HTML, native SVG timelines/assessment maps, CSV registers, project JSON, exact sources, private evidence/history and file manifests. Optional DOCX uses native text/tables; PPTX uses native text/shapes and attached connectors; XLSX uses six editable sheets and linked interval/status formulas. Action priority, categories, tracking and follow-up are retained in the native exports. Office files are editable snapshots: rebuild after source changes; external edits do not synchronize formats. Restrained Office layouts do not reproduce every HTML theme.

    Requirements, delivery and validation boundaries

    Run in the buyer's agent with permitted file and Python tools. No mandatory paid API, seller-hosted backend or remote log upload. The core uses Python 3.10+ standard library. Optional Word/PowerPoint require python-docx/python-pptx. Optional Excel uses host-provided Node.js and @oai/artifact-tool, or permitted host spreadsheet tools with unavailable formats disclosed. No silent global dependency installation. Direct source import supports UTF-8 text; retain binary originals separately and use permitted host extraction/OCR with limitations recorded.

    Agensi loads instructions on demand. No independently installed or downloadable Skill package is promised. Generated user artifacts are distinct from the reusable Skill runtime; the helper does not copy its runtime/catalogue into the work pack. Agensi buyer auxiliary-file loading, temporary relative-file execution, optional dependencies and generated-work retrieval have not been verified in a real buyer account. Platform review is requested to verify these before approval. Microsoft Office desktop edit/save and independent real-incident customer acceptance also remain unverified. Local tests and previews do not prove those gates.

    Creator-authored code and fictional fixtures include the MIT notice. Marketplace access/distribution remain subject to Agensi terms; user inputs retain their rights. Private packs contain original logs, excerpts and history. Share/customer reports retain narrative, IDs, source names and context: review access and wording before external use. Generation does not authorize production changes, notifications or publication.

    Not live incident response, automatic root-cause discovery, ticket synchronization or compliance certification. Structural evidence checks are not authenticity/semantic proof. UTF-8 helper intake only; host extraction needed for binary sources. Customer view is not anonymization. Complex impact edits use project/agent workflow. Office snapshots do not synchronize external edits. Agensi buyer execution/retrieval, Office desktop edit-save and real-customer incident acceptance remain unverified.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

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

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    Requires

    Python 3.10+
    Python

    Permissions

    Read Files
    Write Files

    Allowed Hosts

    127.0.0.1 (optional local workbench)

    File Scopes

    User-selected
    incident
    source
    files
    New
    generated
    artifact/project
    revisions
    Temporary
    runtime
    allowed
    by
    host/platform

    Local helper does not fetch production logs or issue tracker data, send messages, change production or upload sources. Private outputs include original logs/evidence; review access before sharing.

    Listed22 days ago
    Updated14 days ago

    What's inside

    Frequently Asked Questions

    Supply selected logs, alerts, change records, responder notes, affected service/scope, review owner, audience and desired outputs. Keep original files and explicit timestamp offsets. The agent prepares the project; normal review does not require manual JSON authoring. Ambiguities that change conclusions need clarification.

    No. It separates observed facts, hypotheses, rejected explanations and unresolved causes. Supported events/relationships need references and actual review. Validators check linkage, time and workflow rules; they do not establish source authenticity or semantic truth. Never treat temporal order or a tidy map as causal proof.

    Yes: HTML, native SVG geometry/text, CSV and project JSON. Optional DOCX uses native text/tables, PPTX native text/shapes/attached connectors and XLSX six editable sheets with formulas. They are snapshots; source changes require rebuilding and external edits do not synchronize. Office desktop edit/save remains unverified.

    96 original fictional worked studies across 24 technical contexts, with four evidence-workflow variants per context and tailored controls. Three actual HTML layouts, twelve visual foundations and three audience views are adaptable examples. They are not 96 distinct investigation methods; Office exports use a restrained common foundation.

    Keep original ISO timestamp literals and explicit offsets; order in UTC. Explicit reviewed endpoints drive single-incident intervals. Unknown/unverified endpoints stay unavailable, overlapping intervals are merged only within the same scope and impact measures retain their supplied basis. No customer/revenue count is inferred. Up to six fractional timestamp digits; greater precision is rejected.

    Owners, due dates, priority, control type, acceptance criteria, verification evidence, named reviewers, tracking references and follow-up notes. Done and verified are distinct. Priority/owner/due filters and review-next prompts help the next meeting. No remote ticket creation/synchronization or notifications. Excel evidence IDs must still be reconciled semantically against the project.

    The local helper preserves original UTF-8 bytes and makes no external source requests. First import clears fictional records/narrative/history. Your agent/platform processes data under its own settings. Private packs contain sources and evidence. Customer filtering omits draft/unsupported material but does not anonymize the remaining content.

    Not yet. Buyer multi-file loading, temporary relative-file execution, optional dependencies and generated-work retrieval require real buyer validation; platform review is requested before approval. No downloadable installed Skill is promised. Core limits: 30 UTF-8 sources/8 MB, 200 events, 24 assessment nodes, 40 links. Split larger reviews with explicit references; complex impact edits use the project/agent workflow.

    New in Business & Operations