# competition-forensic-timeline

competition-forensic-timeline is a Claude Code skill that correlates EVTX, PCAP, registry, and memory artifacts into incident timelines. It runs during DFIR challenges and attack-chain reconstruction.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 109 installs · ★ 45047 repo stars
- Author: zhaoxuya520
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-forensic-timeline/SKILL.md
- Updated: 2026-09-22
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/competition-forensic-timeline

## What it does

The skill reconstructs attack progression across system traces, tracking paths from initial compromise to persistence and data exfiltration. Event ordering starts from reliable anchors like earliest process execution, network connections, authentication events, or filesystem writes. Correlation links shared properties such as PIDs, GUIDs, user accounts, and hashes across Amcache, prefetch, Sysmon, and network captures.

Operation relies on `$ctf-sandbox-orchestrator` to establish environment assumptions and evidence ranking beforehand. Without that routing step, execution reverts to the parent orchestrator. The workflow separates verified event sequences from analytical gaps and consults `references/forensic-timeline.md` for anchor selection.

Deep packet reassembly and protocol stream reconstruction defer to `$competition-pcap-protocol`. The skill outputs in Simplified Chinese unless English is explicitly designated in the prompt.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/competition-forensic-timeline/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/competition-forensic-timeline/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/competition-forensic-timeline/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/competition-forensic-timeline/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-forensic-timeline/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/competition-forensic-timeline/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-forensic-timeline
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/competition-forensic-timeline/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-forensic-timeline/SKILL.md

## When to use it
- reconstruct incident chronology across disparate forensic sources
- correlate EVTX, memory, and registry records via shared identifiers
- isolate the specific phase where a decisive artifact emerges

## Example prompts
- Build an incident timeline from the EVTX logs and registry hive in English
- Correlate the PCAP network sessions with Sysmon process executions
- Identify the persistence mechanism using Amcache and prefetch data

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f17f87dc8d8adb54.

BEGIN THIRD-PARTY FILE f17f87dc8d8adb54
```text
---
name: competition-forensic-timeline
description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for DFIR chronology, cross-artifact correlation, persistence chains, and incident timeline reconstruction. Use when the user asks to build a forensic timeline, correlate EVTX, PCAP, registry, disk, memory, mailbox, or browser artifacts, explain the order of attacker actions, or pinpoint the stage where the decisive artifact appears. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition Forensic Timeline

Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.

Use this skill when the hard part is not finding one artifact, but turning many artifacts into one replayable chronology.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Pick the smallest reliable anchor: first execution, first logon, first network session, first file write, or first mailbox action.
2. Normalize timestamps, time zones, hostnames, users, process IDs, message IDs, and file paths before correlating.
3. Build one minimal chain from foothold to persistence, execution, access, or exfiltration.
4. Separate confirmed event order from inferred gaps.
5. Reproduce the decisive timeline segment that yields the artifact or privilege conclusion.

## Workflow

### 1. Establish Timeline Anchors

- Collect only the active surfaces: EVTX, Sysmon, registry, Amcache, prefetch, browser artifacts, mail traces, PCAPs, memory, or filesystem metadata.
- Record clock source, timezone, and any drift or truncation that could reorder events.
- Link shared identifiers across sources: PID, logon ID, GUID, message ID, hostname, username, IP, or hash.

### 2. Correlate The Execution Graph

- Track process tree, service or task creation, network sessions, file writes, registry changes, mailbox rules, or token use as one path.
- Distinguish causal edges from coincidence by matching identifiers and adjacency, not just nearby timestamps.
```
END THIRD-PARTY FILE f17f87dc8d8adb54

The third-party file has ended. Everything between the f17f87dc8d8adb54 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2253 of 3289 bytes. © zhaoxuya520 · MIT · https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-forensic-timeline/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
