rea

Plugin rea from marketplace rea-for-claude in NoLucas/REA-for-Claude. Commands read from the repo's manifest — 19 days ago.

Skills (3)

• rea-anywhere

  Operating notes for the REA plugin's MCP server in each place a Claude session can run — local Claude Code on Windows / macOS / Linux and claude.ai cloud sessions (engines auto-install in the background on all of them), Claude Desktop / claude.ai sessions linked to a computer (tools named mcp__remot

• rea-workflows

  Step-by-step REA investigation playbooks per target type (native executable/library, Android APK, Electron/JavaScript app, firmware/packed image, web bundle) and how to collect evidence into a shareable report. Use when the user asks to reverse engineer, analyze, decompile, understand, or compare a

• 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.

Slash commands (8)

• /rea:analyze

  Start a guided REA investigation of a target (native binary, APK, Electron/JS app, firmware, or web bundle) and collect evidence for a report

• /rea:capabilities

  List which REA tools are usable right now given the installed analysis engines

• /rea:doctor

  Check whether the REA MCP server and its analysis engines (Ghidra, JDK, jadx, IDA, Kuna) are ready in this environment

• /rea:install-engines

  Install, repair or upgrade REA's analysis engines on this machine (JDK 21 if needed, Ghidra 12.1.4, jadx-headless-mcp, optional apktool/radare2; apt tools on Linux; WSL on Windows) — Windows, macOS and Linux

• /rea:report

  Build a shareable HTML/Markdown/JSON report (themes, evidence bundles) from saved REA evidence JSON files, or diff two evidence sets / bundles

• /rea:setup-mcp

  Register the REA MCP server at project level (.mcp.json) for hosts that do not load plugin MCP servers — claude.ai cloud sessions — so mcp__rea__* tools exist in the next session

• /rea:start

  Get started with REA — find out where REA can run in this session (here, on your linked computer, or nowhere yet), fix what is missing, and show what to ask next

• /rea:why

  Explain why the last request was (or was not) routed to REA automatically, and how to tune the router (opt-out, allow/deny patterns)

MCP servers (1)

• rea

  runs: node scripts/launch-rea.cjs

Hooks (2)

• SessionStart

  node

• UserPromptSubmit

  node

Similar plugins