Reverse Engineer Anything

Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture. 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.

413,790 stars 103,506 forksSoftware Development Plugin marketplace

Install

Claude Code plugin

/plugin marketplace add morluto/rea

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add morluto/rea --skill reverse-engineer-anything

Manual install

git clone --depth 1 https://github.com/morluto/rea.git /tmp/rea
mkdir -p ~/.claude/skills
cp -r /tmp/rea/.agents/skills/reverse-engineer-anything ~/.claude/skills/reverse-engineer-anything

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# REA

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.

## 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.
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](references/connection-and-recovery.md).
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.

Read the full skill on GitHub

Details

Skill name: reverse-engineer-anything
Repository: morluto/rea
Path: .agents/skills/reverse-engineer-anything/SKILL.md
License: MIT
Repo updated: 31 October 2026
Listed in: VoltAgent/awesome-agent-skills

FAQ

What does the Reverse Engineer Anything skill do?

How do I install the Reverse Engineer Anything skill?

Claude Code plugin: /plugin marketplace add morluto/rea. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Reverse Engineer Anything popular?

It lives in morluto/rea, which has 413,790 GitHub stars and 103,506 forks, and is included in 1 curated skill list.

Related skills

Rea Analysis Optimization

414k

morluto/rea

Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.

Testing & QAIn 1 list104k

Rea Changelog Update

414k

morluto/rea

Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

Git & Code ReviewIn 1 list104k

Rea CI Tests Audit

414k

morluto/rea

Audit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.

Testing & QAIn 1 list104k

Firecrawl Build Onboarding

197k

firecrawl/firecrawl

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

Software Development10k

Karpathy Guidelines

227k

multica-ai/andrej-karpathy-skills

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Software DevelopmentIn 3 lists23k

Codebase Design

308k

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Software DevelopmentIn 1 list26k

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.