Back to catalog
Static reviewDevelopment

Skill dossier

building-incident-timeline-with-timesketch

Source declaration

Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation documentation. Use when reconstructing the sequence of events during an incident investigation or when multiple analysts need to jointly tag, annotate, and search a shared DFIR timeline.

The author's original description, preserved in English. It describes intent, not verified performance.

Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation documentation. Use when reconstructing the sequence of events during an incident investigation or when multiple analysts need to jointly tag, annotate, and search a shared DFIR timeline.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation documentation. Use when reconstructing the sequence of events during an incident investigation or when multiple analysts need to jointly tag, annotate, and search a shared DFIR timeline. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Analysis Workflow [Source statement; provisional, not tested. Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L145]
  • Step 1: Create Investigation Sketch [Source statement; provisional, not tested. Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L147]
  • Step 2: Run Built-in Analyzers [Source statement; provisional, not tested. Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L155]
  • Step 3: Search and Filter [Source statement; provisional, not tested. Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L167]
  • Step 4: Build Investigation Story [Source statement; provisional, not tested. Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L190]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L1-L38]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
48.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/building-incident-timeline-with-timesketch/assets/template.mdReference1.6 KB
skills/building-incident-timeline-with-timesketch/LICENSEOther11 KB
skills/building-incident-timeline-with-timesketch/references/api-reference.mdReference2.1 KB
skills/building-incident-timeline-with-timesketch/references/standards.mdReference1.9 KB
skills/building-incident-timeline-with-timesketch/references/workflows.mdReference3.6 KB
skills/building-incident-timeline-with-timesketch/scripts/agent.pyScript6.5 KB
skills/building-incident-timeline-with-timesketch/scripts/process.pyScript12.8 KB
skills/building-incident-timeline-with-timesketch/SKILL.mdInstruction9.3 KB

SKILL.md frontmatter

{
  "name": "building-incident-timeline-with-timesketch",
  "description": "Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation documentation. Use when reconstructing the sequence of events during an incident investigation or when multiple analysts need to jointly tag, annotate, and search a shared DFIR timeline.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "timesketch",
    "timeline-analysis",
    "forensic-timeline",
    "plaso",
    "dfir",
    "incident-investigation",
    "collaborative-forensics"
  ],
  "mitre_attack": [
    "T1059.001",
    "T1021.002",
    "T1547.001",
    "T1053.005",
    "T1070.006"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Executable Denylisting",
    "Execution Isolation",
    "File Metadata Consistency Validation",
    "Content Format Conversion",
    "File Content Analysis"
  ],
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Architecture and Components

    Source-described action candidate under “Architecture and Components”; not verified execution.

  4. 04
    Action

    Deployment

    Source-described action candidate under “Deployment”; not verified execution.

  5. 05
    Action

    Data Ingestion Methods

    Source-described action candidate under “Data Ingestion Methods”; not verified execution.

  6. 06
    Action

    Analysis Workflow

    Source-described action candidate under “Analysis Workflow”; not verified execution.

Inspect all extracted workflow candidates (22 candidate steps)
  1. 07
    Action

    Step 1: Create Investigation Sketch

    Source-described action candidate under “Step 1: Create Investigation Sketch”; not verified execution.

  2. 08
    Action

    Step 2: Run Built-in Analyzers

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  3. 09
    Action

    Browser Search Analyzer: Extracts search queries from browser history

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  4. 10
    Action

    Chain of Events Analyzer: Links related events (download -> execute)

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  5. 11
    Action

    Domain Analyzer: Extracts and categorizes domain names

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  6. 12
    Action

    Feature Extraction Analyzer: Identifies IPs, URLs, hashes

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  7. 13
    Action

    Geo Location Analyzer: Maps events to geographic locations

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  8. 14
    Action

    Similarity Scorer: Finds similar events across timelines

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  9. 15
    Action

    Sigma Analyzer: Matches events against Sigma detection rules

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  10. 16
    Action

    Account Finder: Identifies user account activity patterns

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  11. 17
    Action

    Tagger: Applies labels based on predefined rules

    Source-described action candidate under “Step 2: Run Built-in Analyzers”; not verified execution.

  12. 18
    Action

    Step 3: Search and Filter

    Source-described action candidate under “Step 3: Search and Filter”; not verified execution.

  13. 19
    Action

    Step 4: Build Investigation Story

    Source-described action candidate under “Step 4: Build Investigation Story”; not verified execution.

  14. 20
    Action

    Key Data Sources for Timeline Building

    Source-described action candidate under “Key Data Sources for Timeline Building”; not verified execution.

  15. 21
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  16. 22
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

33 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

13 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 13 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

17 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 17 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/building-incident-timeline-with-timesketch/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/building-incident-timeline-with-timesketch/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/building-incident-timeline-with-timesketch
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.