windows-kernel-security — Claude Code skill: kernel analysis
windows-kernel-security — a skill for analyzing Windows kernel structures, drivers, security mechanisms and forensics. For researchers working on game security and authorized kernel analysis.
MIT 239 installs ★ 3,784 updated 2026-10-25
npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a claude-codeWhat windows-kernel-security does
This skill maps undocumented structures, offsets and allocator behavior to specific Windows builds and symbols. It separates documented contracts, observed state and inference-based findings.
Content is organized into foundations (driver surfaces, PatchGuard, DSE, VBS/HVCI, Secure Boot), driver observation (callbacks, IRQL, APCs, hooking, ETW), memory and forensics (pool architecture, access patterns, dumps, tools), and threats and virtualization (vulnerable drivers, hypervisor defenses). Includes routing to repository resources and guidance on source selection.
Requires understanding of Windows versions and exact symbols for each build. For DMA attack work, reference dma-attack-techniques; for version-sensitive conclusions, use game-security-research-rigor.
What it helps with
- map kernel memory structure and allocator behavior to your Windows build
- examine driver callbacks, IRQL levels and APC behavior
- research kernel protection: PatchGuard, DSE, VBS/HVCI
- interpret memory dumps and ETW traces
- locate undocumented offsets and structures in the kernel
Example prompts for the agent
- Which callbacks intercept at IRQL > DISPATCH_LEVEL on Windows 22H2?
- How do I check DSE and PatchGuard status in this build?
- Show the kernel memory pool architecture and allocator addresses for this Windows version
How to install windows-kernel-security
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a claude-code2Manually: put the files in place
~/.claude/skills/windows-kernel/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/windows-kernel/
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a codex2Manually: put the files in place
.agents/skills/windows-kernel/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a cursor2Manually: put the files in place
.cursor/skills/windows-kernel/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gmh5225/awesome-game-security .claude/skills/windows-kernel2Manually: put the files in place
.github/skills/windows-kernel/SKILL.md1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a gemini-cli2Platform CLI
gemini skills install https://github.com/gmh5225/awesome-game-security --path .claude/skills/windows-kernelManually: put the files in place
.devin/skills/windows-kernel/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a opencodeClaude.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-kernel-security
How do I install windows-kernel-security in Claude Code?
Run npx skills add gmh5225/awesome-game-security --skill windows-kernel-security -a claude-code, then check ~/.claude/skills/windows-kernel/SKILL.md.
What does windows-kernel-security do?
It helps analyze Windows kernel structures, drivers, callbacks, IRQL, memory protection, PatchGuard, DSE, VBS/HVCI and forensics artifacts tied to your specific Windows build and symbols.
Which platforms support this skill?
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. For GitHub Copilot, use gh skill install gmh5225/awesome-game-security windows-kernel.
Source text
SKILL.md · MIT
--- name: windows-kernel-security description: Analyze Windows driver trust, callbacks, IRQL, kernel memory, DSE, PatchGuard, VBS/HVCI, ETW, crash evidence, and build-specific internals for authorized game-security research. --- # Windows kernel security Match undocumented structures, offsets, globals, and allocator behavior to the exact Windows build and symbols. Separate documented contracts, observed state, and inference. ## Topic routing - [Foundations and security](references/foundations-and-security.md) for driver surfaces, symbols, PatchGuard, DSE, VBS/HVCI, and Secure Boot. - [Drivers and observation](references/drivers-and-observation.md) for callbacks, IRQL, APCs, driver structure, hooking, and ETW. - [Memory and forensics](references/memory-and-forensics.md) for pool architecture, memory access, dumps, and tools. - [Threats and virtualization](references/threats-and-virtualization.md) for vulnerable drivers, boot threats, PatchGuard research, and hypervisor defenses. - [Repository resources](references/repository-resources.md) and [repository map](references/repository-map.md) for source selection. Use `dma-attack-techniques` for device-originated memory access and `game-security-research-rigor` for version-sensitive conclusions.
© gmh5225 · MIT · gmh5225/awesome-game-security