More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Incident Timeline Evidence Review

    1

    Diagnose and repair incident timelines, source evidence, action chronology, conflicting timestamps, decisions, and recovery claims.

    $8.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Incident Timeline Evidence Review

    Incident Timeline Evidence Review

    Example session with this skill installed

    Review the timeline for the DB outage. Sources: slack-export.txt and db-logs.csv in /docs. Map the detection to the first failover attempt and flag any gaps.

    • Read your context and instructions
    • Compiled the incident timeline evidence
    • Generated the data export

    I have analyzed the Slack export and database logs to reconstruct the timeline for the database outage. I focused on the period between the first 'High Latency' alert and the successful failover completion.

    Incident Timeline & Evidence Review

    Source Register

    IDSourceTypeTime Range (UTC)
    S1slack-export.txtCommunication14:02 - 15:45
    S2db-logs.csvSystem Logs13:50 - 16:00

    Evidence-Backed Chronology

    Timestamp (UTC)EventSourceStatus
    14:02:12First Latency 500ms+ alert triggeredS2Verified
    14:05:45On-call engineer (Alice) acknowledges in #opsS1Verified
    14:10:00First failover command issued via CLI-GAP
    14:12:30Log entry: Secondary node promotion failed: timeoutS2Verified
    14:15:20Decision to manually restart primaryS1Verified

    Conflicts and Gaps

    Gap: Missing CLI Logs. S1 mentions a failover attempt at 14:10:00, but S2 shows no connection attempts until 14:12:30. The actual command execution log is missing from the workspace.
    *

    Conflict: Detection Time. The official status page (referenced in S1) claims detection at 14:00:00, but the first log-based alert (S2) did not fire until 14:02:12.

    Missing Evidence Needed

    1. CLI History/Audit Log: To confirm the exact time and parameters of the 14:10:00 failover attempt.
    2. Monitoring Config: To understand the 2-minute delay between user-reported latency and system alerts.

    Next steps

    • Retrieve the shell history from the jump host used by Alice.
    • Update the draft post-mortem to reflect the 132-second detection lag.
    • Verify if the secondary node timeout was due to network partition or resource exhaustion.

    incident-timeline-evidence-review.csv

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    What you get

    Verify incident timelines against raw system logs and chat history.Identify specific evidence gaps in post-mortem documentation.Reconcile conflicting timestamps across distributed system logs.Map mitigation actions to specific decision points in Slack or Teams.

    About this skill

    Incident Timeline Evidence Review is a bounded ToolForge Labs workflow. Diagnose and repair incident timelines, source evidence, action chronology, conflicting timestamps, decisions, and recovery claims. Works from full repositories or partial context such as snippets, logs, configuration, traces, and architecture notes. Produces concrete repairs or evidence-backed review outputs while preserving existing product/security policy.

    It works from a full repository or partial evidence such as snippets, logs, configuration, traces, tickets, and architecture notes. The skill preserves existing product and security policy, separates verified facts from assumptions, avoids invented execution claims, and produces concrete repair or review steps with focused deterministic validation or traceable evidence.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 21 days ago

    • Passed all security checks, Safe to install

    Listed21 days ago

    What's inside

    Frequently Asked Questions