Competition Forensic Timeline logo

Competition Forensic Timeline

CommunityPopular
zhaoxuya520
competition-forensic-timeline

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.

Overview

Publisherzhaoxuya520
Repositoryreverse-skill
Skill namecompetition-forensic-timeline
Stars
36.3K
Forks
5K
Bundled files
2
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by zhaoxuya520 on GitHub. Read the source before you install it.

Installation

Install the Competition Forensic Timeline AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zhaoxuya520/reverse-skill.git /tmp/reverse-skill
mkdir -p .claude/skills
cp -r /tmp/reverse-skill/CTF-Sandbox-Orchestrator/competition-forensic-timeline .claude/skills/competition-forensic-timeline
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Competition Forensic Timeline in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Competition Forensic Timeline on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Competition Forensic Timeline is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Competition Forensic Timeline AI skill do?

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.

Why use Competition Forensic Timeline on TypingMind?

Because you install it once and use it with any model. Competition Forensic Timeline is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Competition Forensic Timeline in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-forensic-timeline. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Competition Forensic Timeline?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Competition Forensic Timeline?

As many as you like. As long as a model supports skills, you can use Competition Forensic Timeline with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Competition Forensic Timeline AI skill free?

Yes. It is published on GitHub by zhaoxuya520 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
JuliusBrussee logo

Caveman Discover

JuliusBrussee
CommunityPopular

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

6.2K
106.3K
Instructions
View
JuliusBrussee logo

Caveman Manage

JuliusBrussee
CommunityPopular

Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.

6.2K
106.3K
Instructions
View
JuliusBrussee logo

Caveman Setup

JuliusBrussee
CommunityPopular

Wire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.

6.2K
106.3K
Instructions
View
nexu-io logo

Eng Runbook

nexu-io
OrganizationPopular

An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief…

11.2K
96.7K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇