bluehammer-vulnerability-poc — Claude Code skill: build and read
A skill that walks the agent through the BlueHammer repo: building the C exploit, running it, and reading the vulnerability code. For isolated labs only.
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a claude-codeWhat bluehammer-vulnerability-poc does
BlueHammer is a C proof-of-concept that demonstrates one specific vulnerability. The repo is a research artifact: it documents the bug, ships the exploit, and carries a PGP signature so you can check authenticity. The skill hands the agent that context instead of leaving it to guess how the code builds and runs.
Inside are working command patterns. Clone with git clone, verify the signed README against the author's key, build a single file with gcc and flags like -fno-stack-protector and -no-pie, then run the binary with a target argument. A separate section covers the usual mistakes in PoCs of this kind: off-by-one writes, a missing null terminator, a wrong size in malloc, a shifted offset in the payload. Debugging gets its own pass with gdb, strace and checksec, plus a Python harness that brute-forces the crash offset.
The author flags known bugs in the PoC, so it may not work as-is. That is the reason to read the source closely rather than expect a clean run. Keep it inside an authorized isolated environment — the code is a demonstration, meant for defense and study.
What it helps with
- build a single-file C exploit with no documented build system
- verify the PGP signature on the README before running anything
- find the offset that overwrites the return address
- audit PoC source for size and bounds mistakes
- debug a crashing binary under gdb and strace
Example prompts for the agent
- use bluehammer, help me build the PoC from source
- read the bluehammer vulnerability code and find the buffer size bug
- set up bluehammer in an isolated lab and run it with a target argument
How to install bluehammer-vulnerability-poc
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a claude-code2Manually: put the files in place
~/.claude/skills/bluehammer-vulnerability-poc/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bluehammer-vulnerability-poc/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a codex2Manually: put the files in place
.agents/skills/bluehammer-vulnerability-poc/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a cursor2Manually: put the files in place
.cursor/skills/bluehammer-vulnerability-poc/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills bluehammer-vulnerability-poc2Manually: put the files in place
.github/skills/bluehammer-vulnerability-poc/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/bluehammer-vulnerability-pocManually: put the files in place
.devin/skills/bluehammer-vulnerability-poc/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -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 bluehammer-vulnerability-poc
How do I install bluehammer-vulnerability-poc in Claude?
Run npx skills add reason-machines/trending-skills --skill bluehammer-vulnerability-poc -a claude-code. The skill lands in ~/.claude/skills/bluehammer-vulnerability-poc/SKILL.md.
What does bluehammer-vulnerability-poc do?
It gives the agent context for the BlueHammer repo: building the PoC, running it, and reading the vulnerability code. It also points out common bugs in exploits like this one.
Is it safe to run this PoC?
The code is a demonstration for research and defensive work. The author notes known bugs in the PoC, so run it only in an authorized isolated environment.