Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/ghidra
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.
Passed 21 of 22 test cases with the skill, and 6 of 22 without it.
and 15 more in the full report
16 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When analyzing binary auth_daemon using the headless script, I want to keep the underlying Ghidra project directory on disk after execution instead of letting the script clean it up automatically. Output goes to ./auth_out. What flag manages this?
| Checked | Without skill | With skill |
|---|---|---|
| Includes --keep-project flag | Missed | Passed |
The instructions your model reads when the skill loads.
Perform automated reverse engineering using Ghidra's analyzeHeadless tool. Import binaries, run analysis, decompile to C code, and extract useful information.
| Task | Command |
|---|---|
| Full analysis with all exports | ghidra-analyze.sh -s ExportAll.java -o ./output binary |
| Decompile to C code | ghidra-analyze.sh -s ExportDecompiled.java -o ./output binary |
| List functions | ghidra-analyze.sh -s ExportFunctions.java -o ./output binary |
| Extract strings | ghidra-analyze.sh -s ExportStrings.java -o ./output binary |
| Get call graph | ghidra-analyze.sh -s ExportCalls.java -o ./output binary |
| Export symbols | ghidra-analyze.sh -s ExportSymbols.java -o ./output binary |
| Find Ghidra path | find-ghidra.sh |
brew install --cask ghidraThe skill automatically locates Ghidra in common installation paths. Set GHIDRA_HOME environment variable if Ghidra is installed in a non-standard location.
./scripts/ghidra-analyze.sh [options] <binary>
Wrapper that handles project creation/cleanup and provides a simpler interface to analyzeHeadless.
Options:
-o, --output <dir> - Output directory for results (default: current dir)-s, --script <name> - Post-analysis script to run (can be repeated)-a, --script-args <args> - Arguments for the last specified script--script-path <path> - Additional script search path-p, --processor <id> - Processor/architecture (e.g., x86:LE:32:default)-c, --cspec <id> - Compiler spec (e.g., gcc, windows)test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.