reverse-engineer-anything

Topics in the source

• REA
• Connect only when needed
• Route the target first
• Work summary-first
• Plan broader investigations
• Read only the relevant guide
• Finish the task

Use REA when a claim depends on a shipped binary or package, decompilation, requested 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. Installing this skill supplies instructions; it does not register the REA MCP server, install analysis engines, or add tools to an already-running agent. The exception is a Claude Code or Codex plugin install: the plugin bundles this skill and registers its own rea server, outside the state that rea setup and rea doctor manage. 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 block

This is an excerpt. Refer to the complete source and its current requirements.