Menu

Individual skill

forensics-pro

0upvotes

Conduct digital forensics investigations — evidence acquisition, timeline analysis, and court-ready documentation.

skills/forensics-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Digital forensics is the science of reconstructing what happened on systems: what the attacker did, when, and what data was affected. It serves incident response, legal proceedings, and HR investigations. The work lives or dies on **method**: forensically sound acquisition, chain of custody, and timeline analysis that turns scattered artifacts into a coherent story.

This skill covers the end-to-end methodology — acquisition, analysis, timeline building, and reporting — for practitioners supporting incidents and investigations.

Forensics is the discipline of being right when it matters most — under legal scrutiny, executive pressure, and incomplete data. The methodology exists because memory is fallible and tools have opinions: hash everything, document every step, corroborate across artifacts, and state uncertainty plainly. 'We could not determine X because Y' is a professional answer; guessing is not.

## When to use

- Supporting an active incident: which hosts were touched, what data left.
- HR/legal investigations: policy violations, data theft, insider activity.
- Building a defensible timeline for breach notification or litigation.
- Validating scope before eradication and recovery decisions.
Back to top