reverse-engineer-anything
Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.
morluto · 站主发布
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add https://github.com/morluto/rea/tree/7c207c79512f6baa70f4ed9d7d5334ab2d62f3ac/.agents/skills/reverse-engineer-anything --skill "reverse-engineer-anything"技能说明
name: reverse-engineer-anything description: Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. metadata: version: "39"
REA
Use REA when a claim depends on a shipped binary or package, decompilation, passive application runtime evidence, or comparison with behavior not established by available source. For ordinary analysis of a complete source repository, use normal repository tools and do not run REA readiness or provider commands.
Connect only when needed
Installing this skill supplies instructions; it does not register the REA MCP server, install analysis engines, or add tools to an already-running agent.
If REA tools are available and their registration is not known to be stale, proceed directly to the target. Do not run diagnostics or setup before every investigation. Use the connected server's actual tool list and input schemas; a skill installed from repository main may describe capabilities absent from an older npm release. Keep complete inline Evidence when that server does not advertise retained references.
If tools are absent, a call is blocked by the client, or a required provider is unavailable, read connection and recovery. Diagnose the observed blocker, continue useful supported work, and resume the original task after repair. Client approval, shell PATH, registration and engine availability have different remedies; avoid repeating setup for all of them.
Prefer an existing rea CLI. When none is installed and REA package acquisition
is within the authorized scope, use npx -y rea-agents@latest in its place.
Configuration repair starts with a read-only setup plan; show paths, backups and
skill replacement before applying authorized changes. Preserve existing approval
and target-execution boundaries. REA setup never installs or upgrades unrelated
software, including Node.js, npm, Homebrew, Java, Ghidra, IDA, JADX, Binwalk or Unblob.
Route the target first
Choose the first tool from the target the user supplied. Use open_binary for
active-target native or archive workflows; target-free tools take their own
explicit path or endpoint and do not need it.
- ASAR or extracted JavaScript/Electron tree:
analyze_javascript_application. - Archive/package member inventory (ZIP/APK/IPA/MSIX/AppX or DMG):
open_binarywith the supplied local path; useinspect_artifactwhen its graph and findings help answer the question. - Android APK code, classes, methods, or incoming references:
inspect_android_package, then focused Android tools when advertised. Archive member inventory still uses the archive route above. - Managed PE/CLI assembly:
inspect_managed_artifact. - Firmware image:
inspect_firmware_regionswhen advertised. Useextract_firmwarewhen extraction is requested, with a caller-selected new absolute output directory. These tools use caller-supplied Binwalk/Unblob on Linux; see the firmware guide. - .NET NativeAOT PE/ELF: native Ghidra analysis. Native code can yield pseudocode;
consult the NativeAOT workflow in
references/native-and-artifacts.mdfor optional metadata recovery and its supported host/layout boundary. - User-owned browser page already open:
list_browser_targets. - Retained HAR/native mitmproxy capture:
inspect_web_network_capture. Select original record ordinals when useful; inspect producer fields and byte/number sidecars without fetching recorded URLs or claiming live attribution. See historical captures for the exact upstream profile and credential exclusions. - User-owned Electron runtime already open:
list_electron_targets. - Explicit local WebAssembly artifact:
inspect_wasm_artifact. Supply WABT 1.0.42 throughREA_WABT_BIN_DIRECTORY; retain exact byte/tool identity and decoded WAT. Select JavaScript glue and candidate paths explicitly and preserve URL/path ambiguity. No implicit fetch or target execution; WAT is not original source. See the WASM guide. - Explicit local EVM bytecode carrier:
inspect_evm_interfacewith caller-selectedraworhexencoding. Preserve carrier/decoded digests and treat selectors, argument strings and mutability as inferred candidates; this performs no chain lookup or target execution. See the EVM bytecode guide. - Explicit Linux ELF file for offline layout, symbols, relocations or static
mitigation evidence:
inspect_binary_layout. This target-free operation uses caller-supplied pwntools without opening a disassembler database. Preserve its raw locations and inference/coverage limits; see the offline binary guide. - Supplied Linux x86-64 ELF core:
inspect_recorded_crash. Read every recorded thread, raw note and source-bound register without opening a live target. Historical PIDs do not select live processes. Requestinclude_debugger_contextonly when core-only mapping candidates help; see the recorded crash guide. - PE resource type/name/language trees and static icon group references:
inspect_pe_resourceswith an explicit path. This portable operation requires no active target or engine; opaque payloads retain file ranges and SHA-256. - Native executable, library, or analysis database:
open_binary, then use focused analysis tools directly; callbinary_overviewwhen metadata or inventory context is usefu