windows-artifact-forensics-registry-artifacts — Claude Code skill
windows-artifact-forensics-registry-artifacts is a Claude Code skill for Windows registry analysis. It tracks persistence mechanisms, GUI program runs, and USB device connection history.
no license ★ 73 updated 2026-11-15
npx skills add W4L33Dx/Cyber-Monster --skill windows-artifact-forensics-registry-artifacts -a claude-codeWhat windows-artifact-forensics-registry-artifacts does
This skill guides Windows registry investigations during digital forensics. It classifies registry artifacts by what they actually confirm: Run and Services keys demonstrate configuration intent rather than execution, while UserAssist stores GUI execution counts and timestamps in ROT13 format. Device connection records come from USBSTOR and MountedDevices.
Hives pulled from active machines are treated as dirty because recent updates sit inside .LOG1 and .LOG2 files. Parsing the main hive without replaying these transaction logs hides the latest persistence writes. For user attribution, the workflow maps SIDs to filesystem paths via ProfileList, and resolves the active configuration set in SYSTEM hives through Select\Current.
What it helps with
- reconstruct external drive attachment history from
USBSTOR - detect persistence mechanisms inside
Runkeys and system services - confirm graphical executable launches through
UserAssistentries - parse dirty registry hives after replaying transaction logs
Example prompts for the agent
- Analyze the SYSTEM hive and find the active control set using Select\Current
- Inspect Run keys and UserAssist entries in the extracted hive for persistence
- Extract USB drive connection history from USBSTOR and MountedDevices artifacts
How to install windows-artifact-forensics-registry-artifacts
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill windows-artifact-forensics-registry-artifacts -a claude-code2Manually: put the files in place
~/.claude/skills/windows-artifact-forensics-registry-artifacts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/windows-artifact-forensics-registry-artifacts/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill windows-artifact-forensics-registry-artifacts -a codex2Manually: put the files in place
.agents/skills/windows-artifact-forensics-registry-artifacts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill windows-artifact-forensics-registry-artifacts -a cursor2Manually: put the files in place
.cursor/skills/windows-artifact-forensics-registry-artifacts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install W4L33Dx/Cyber-Monster blue-team/digital-forensics/windows-artifact-forensics-registry-artifacts2Manually: put the files in place
.github/skills/windows-artifact-forensics-registry-artifacts/SKILL.md1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill windows-artifact-forensics-registry-artifacts -a gemini-cli2Platform CLI
gemini skills install https://github.com/W4L33Dx/Cyber-Monster --path blue-team/digital-forensics/windows-artifact-forensics-registry-artifactsManually: put the files in place
.devin/skills/windows-artifact-forensics-registry-artifacts/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 windows-artifact-forensics-registry-artifacts
How do I install windows-artifact-forensics-registry-artifacts in Claude Code?
Run npx skills add W4L33Dx/Cyber-Monster --skill windows-artifact-forensics-registry-artifacts -a claude-code.
What does windows-artifact-forensics-registry-artifacts do?
It provides forensic decision rules to inspect Windows registry hives, separating configured persistence from verified executions and external device events.
What is required to inspect live-captured hives with this skill?
You need the primary hive file alongside its .LOG1 and .LOG2 transaction logs to replay pending writes before analysis.