Incident Timeline Evidence Builder

    1

    Transforms logs, chats, and witness reports into a traceable, evidence-linked incident chronology for investigators.

    $6.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Incident Timeline Evidence Builder

    Example session with this skill installed

    Build a timeline for INC-88 from these: Monitoring alert at 14:02 UTC, Support ticket 551 at 14:15 UTC, and an engineer's Slack message saying 'Database looks slow' at 15:10 BST.

    • Read your context and instructions
    • Compiled the incident timeline evidence

    I have processed the supplied artifacts for INC-88. The chronology highlights a timezone discrepancy between the UTC system logs and the BST communication records. ## Incident Timeline Evidence Pack ### 1. Scope and Confidence Statement - **Incident ID:** INC-88 - **Covered Period:** 14:02 UTC to 14:15 UTC (System), 14:10 BST (Communication) - **Time-Standard:** Normalized to UTC - **Materials:** 1x Monitoring Alert, 1x Ticket Extract, 1x Slack Snippet - **Reliability:** Medium; Requires confirmation of Slack user's local clock synchronization. ### 2. Evidence Source Catalogue | Evidence ID | Source/type | Custodian | Original reference/link | Timestamp basis | Integrity status | | :--- | :--- | :--- | :--- | :--- | :--- | | E001 | Monitoring Alert | System | ALRT-992 | UTC / Server Log | Verified Log | | E002 | Support Ticket | Service Desk | TKT-551 | UTC / DB Entry | System Generated | | E003 | Slack Message | IT Dept | MSG-8821 | BST / Client App | Witness/Chat | ### 3. Timestamp Normalisation Record | Evidence ID | Original timestamp | Stated timezone | Normalised time | Clock reliability | Conversion notes | | :--- | :--- | :--- | :--- | :--- | :--- | | E001 | 14:02 | UTC | 14:02:00 UTC | High | Direct ingest | | E002 | 14:15 | UTC | 14:15:00 UTC | High | Database record | | E003 | 15:10 | BST | 14:10:00 UTC | Medium | Converted from BST (UTC+1) | ### 4. Evidence-Linked Chronology | Event ID | Normalised time | Original time | Action/observation | Source IDs | Evidence class | Confidence | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | EV01 | 14:02:00 UTC | 14:02 | System Alert Triggered | E001 | Automated Alert | High | | EV02 | 14:10:00 UTC | 15:10 BST | "Database looks slow" | E003 | Communication | Medium | | EV03 | 14:15:00 UTC | 14:15 | Ticket TKT-551 created | E002 | System Record | High | ### 5. Contradictions and Unresolved Events - **Conflict ID:** C001 - **Competing evidence:** Slack message (14:10 UTC) vs Alert (14:02 UTC). - **Why it matters:** Determines if the human observation preceded or followed the automated detection. - **Verification action:** Request Slack audit log for absolute UTC message timestamp. **Next steps** - Verify the Slack user's local timezone settings to confirm the 14:10 UTC normalization. - Request the Database Performance logs for the period between 14:00 and 14:15 UTC. - Obtain the full message thread for E003 to identify any earlier mentions of latency.

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

    About this skill

    Reconstructing a clear sequence of events after a cyber, safety, or operational incident is difficult when data is scattered across disparate logs, chats, and witness reports. Inconsistent timezones and missing evidence often lead to unreliable chronologies and flawed root-cause analysis. This skill transforms fragmented records into a defensible, evidence-linked incident chronology for investigators and auditors. It prioritizes provenance, ensuring every event traces back to a specific source while explicitly flagging contradictions, clock drift, and data gaps. ## What it does - **Builds source catalogues** by registering unique evidence IDs, types, and integrity status for every artifact. - **Normalizes timestamps** across different timezones and formats while preserving original strings to prevent conversion errors. - **Maps evidence-linked chronologies** that distinguish between system-observed actions, communications, and witness recollections. - **Identifies contradictions** between competing accounts or differing log clocks without forcing a resolution. - **Generates preservation requests** by identifying missing originals and high-priority artifacts needed for a complete record. ## How it works 1. **Define scope** by establishing the incident window and documenting supplied materials. 2. **Extract event candidates** from logs, tickets, and messages while maintaining verbatim accuracy and source references. 3. **Analyze and merge** records to create a unified timeline that highlights gaps, overlaps, and uncertainty intervals. 4. **Deliver a neutral pack** containing the event register, source index, and a strictly evidence-based narrative. ## Frameworks & tools Works with raw event logs, CSV exports, email headers, ticket histories (Jira/ServiceNow), chat transcripts (Slack/Teams), and witness statements. ## Why this beats prompting it yourself Generic prompts often hallucinate connections or silently normalize timezones by assumption, which destroys evidentiary value. This skill uses a structured investigative framework that preserves uncertainty and separates analyst inference from documented fact. ## Use cases - **Post-incident reviews** to build a neutral sequence of events for stakeholder reporting. - **Cyber-forensic preparation** by organizing raw logs before handing them to a specialist team. - **Audit response** to demonstrate a clear trail of actions taken during a service outage. - **Workplace investigations** by merging conflicting witness accounts with digital activity logs. ## Known limitations Does not independently authenticate evidence or determine legal liability. It cannot acquire private records automatically and requires user-supplied artifacts.

    Does not authenticate evidence or determine legal liability. Requires manual artifact input. Cannot resolve time conflicts without corroborating data.

    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 17 days ago

    Permissions

    Write Files
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    The skill accepts a wide range of raw data, including CSV/JSON event logs, email headers, Jira or ServiceNow ticket histories, Slack/Teams transcripts, and text-based witness statements.

    Unlike generic AI prompts that may 'fill in the blanks' with hallucinations, this skill uses a structured framework that preserves uncertainty, flags clock drift, and maintains a strict link between every event and its specific source ID.

    The skill automatically normalizes disparate timezones into a single reference standard while simultaneously preserving the original timestamp strings to ensure auditability and prevent conversion errors.

    No, the skill is designed to be tool-agnostic; it works with your existing AI agent to process user-supplied artifacts and does not require direct access to your internal logging systems.

    Upon purchase, you receive the full skill configuration and logic optimized for investigative workflows, along with documentation on how to structure your input data for the best results.

    The skill is highly effective at identifying conflicting accounts or 'data gaps,' but it does not independently verify the authenticity of a file or assign legal liability for an incident.

    New in Technical Documentation