What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
- files
- 4
- Markdown files
- 2
- scripts
- 1
- references
- 1
- Size
- 34 KB
- Structural complexity
- Low
File inventory
PathTypeBytes
skills/analyzing-prefetch-files-for-execution-history/LICENSEOther11 KB
skills/analyzing-prefetch-files-for-execution-history/references/api-reference.mdReference3.1 KB
skills/analyzing-prefetch-files-for-execution-history/scripts/agent.pyScript8 KB
skills/analyzing-prefetch-files-for-execution-history/SKILL.mdInstruction11.9 KB
SKILL.md frontmatter
{
"name": "analyzing-prefetch-files-for-execution-history",
"description": "Parse Windows Prefetch files (versions 17, 23, 26, 30) with tools like PECmd, WinPrefetchView, or python-prefetch to determine program execution history, including run counts, execution timestamps, and referenced files/DLLs. Use when building a timeline of program execution on a Windows system, confirming whether a suspicious binary ran, or correlating execution evidence with other forensic artifacts during an investigation.",
"domain": "cybersecurity",
"subdomain": "digital-forensics",
"tags": [
"forensics",
"prefetch",
"windows-artifacts",
"execution-history",
"timeline-analysis",
"evidence-collection"
],
"version": "1.0",
"author": "mahipal",
"license": "Apache-2.0",
"nist_csf": [
"RS.AN-03",
"DE.AE-02",
"RS.MA-01"
],
"mitre_attack": [
"T1059.001",
"T1003.001",
"T1021.002",
"T1567.002"
]
}