competition-forensic-timeline — Claude Code skill
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.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a claude-codeWhat competition-forensic-timeline 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.
What it helps with
- 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 for the agent
- 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
How to install competition-forensic-timeline
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a claude-code2Manually: put the files in place
~/.claude/skills/competition-forensic-timeline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-forensic-timeline/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a codex2Manually: put the files in place
.agents/skills/competition-forensic-timeline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a cursor2Manually: put the files in place
.cursor/skills/competition-forensic-timeline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-forensic-timeline/SKILL.md2Manually: put the files in place
.github/skills/competition-forensic-timeline/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-forensic-timelineManually: put the files in place
.devin/skills/competition-forensic-timeline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-forensic-timeline
How to install competition-forensic-timeline in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-forensic-timeline -a claude-code. The definition is saved to ~/.claude/skills/competition-forensic-timeline/SKILL.md.
What does competition-forensic-timeline do?
It turns multiple forensic artifacts into a single sequential timeline for DFIR challenges. The tool connects system events, memory traces, and network logs into an evidence-backed chain.
What is required before using competition-forensic-timeline?
It operates strictly downstream from $ctf-sandbox-orchestrator. That parent orchestrator must be active first to define sandbox baselines, asset boundaries, and evidence focus.
Source text
SKILL.md · MIT
--- 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. - Keep raw artifact and parsed summary side by side so every step can be traced back. ### 3. Compress To The Decisive Story - Reduce the timeline to the smallest sequence that proves initial access, persistence, lateral movement, collection, or artifact recovery. - Call out missing validation steps separately instead of mixing them into confirmed chronology. - If the task becomes mainly about malware config extraction or a Windows pivot edge, switch to the tighter specialized skill. ## Read This Reference - Load `references/forensic-timeline.md` for anchor selection, cross-source correlation, and evidence packaging. - If the hard part is packet reassembly, protocol framing, or transferred-object extraction from a capture, prefer `$competition-pcap-protocol`. ## What To Preserve - Source file paths, event IDs, logon IDs, message IDs, PIDs, hashes, and timestamps with timezone noted - One compact timeline table or ordered list for the decisive segment - Raw artifacts, parsed output, and inferred edges kept separate
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill