Reverse Engineer Anything (REA)
Rutingslag for REA reverse-engineering verktøykjede; trenger sin egen CLI
Tested · Didn't pass
Hva den gjør
Et rutingsdokument som forteller en agent hvilke av REAs 110 reverse-engineering tools den skal reach for on a binary, an Electron ASAR, a managed PE assembly, an app package or a live browser page, og how to report findings as evidence with observations separated from inferences. Det er en front end only: the analysis itself comes from the rea-agents CLI and MCP server, pluss a Hopper or Ghidra backend for native targets.
Testrapport
The skill file copies in cleanly, but on its own it is inert – it only routes to 110 MCP tools that arrive with 'npx rea-agents setup', and REAs own doctor confirmed the rest is missing too: no Hopper, and Ghidra needs GHIDRA_INSTALL_DIR pointed at an extracted 12.1.2 release. The CLI underneath is real: pointed at Claude.apps app.asar it verified archive integrity and flagged a native binding whose declared SHA-256 did not match the file on disk, and I reproduced both hashes independently. It then refused to analyse further, and did the same on ChatGPT.app – two for two, because code-signed macOS Electron apps routinely carry unpacked native modules that no longer match the header, so a plain asar header parse got further than the skill did. Also worth knowing: the SKILL.md on GitHub declares 111 tools while the published CLI ships 110, a mismatch REAs own doctor is built to flag as drift.
Testet på: 2026-07-28 · Claude Code 2.x (agent harness)
Installer
git clone https://github.com/morluto/rea.git mkdir -p ~/.claude/skills cd rea && cp -r skills/reverse-engineer-anything ~/.claude/skills/reverse-engineer-anything
Kommandoer og eksempelprompter
/reverse-engineer-anythingRutingslag for REA reverse-engineering verktøykjede; trenger sin egen CLI
Skills utløses av vanlige forespørsler — ingen kommandoer å huske. Etter installasjonen aktiverer prompter som disse skillen (på engelsk):
How does the search feature in this Electron app's app.asar work?Decompile this .dylib and tell me exactly what the license check doesCompare v2 and v3 of this .apk and tell me precisely what changed