agentleFS
Sign inStart free
mtarcuremtarcure/claude-vibe-squad/.agents/skills/forensic-timeline-authoring/SKILL.md

forensic-timeline-authoring

Skill220 starsChanged 18 days agoMITView on GitHub

Use when reconstructing an incident from logs, images, records, or other artifacts and the chronology must preserve provenance—normalize clocks, hash and cite each source, label fact versus inference, and leave evidentiary gaps unknown.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every entry cites a source and hash.

    line 19
  2. Distinctive:

    No fabricated or interpolated events.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Forensic Timeline Authoring

Reconstruct an evidence-preserving incident timeline that separates observed fact from inference.

Steps

  1. Collect artifacts with metadata: source, collection time, collector, hash, sensitivity.
  2. Normalize clocks and time zones; note any clock skew or unsynced sources.
  3. Order events on a single timeline; cite the source (and hash) for each entry.
  4. Label every line as observed fact, inference, recommendation, or executed action.
  5. Mark chain-of-custody gaps and unrecoverable periods as unknown — never fill with plausible guesses.

Acceptance

  • Every entry cites a source and hash; fact vs inference is labeled per line.
  • Clock skew is noted; gaps are marked unknown.
  • No fabricated or interpolated events.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free