domains / families / software-engineering / reverse-engineer-anything

reverse-engineer-anything

authentic

Use REA to investigate shipped apps, binaries, packages, and runtimes; trace features with evidence, compare versions, or guide reconstruction. Skip ordinary source-code analysis.

When to use

• Use when a claim depends on a shipped application, binary, package, or requested runtime evidence.
• Use for decompilation, evidence-backed feature traces, version comparisons, or investigation-guided reconstruction.
• Skip REA for ordinary source-code analysis of a complete repository.

When not to use

• The skill supplies investigation guidance; it does not register the REA MCP server or install analysis engines.
• Native-analysis availability depends on the selected provider, host, and target format. Hopper is separate licensed software; Ghidra and IDA are bring-your-own.
• Static analysis does not establish runtime behavior or recover original source code. Report provider-specific coverage, partial results, and unknowns.
• REA runs analysis locally, but the connected model provider may have separate data-handling policies.

Skill page

Source