agentleFS
Sign inStart free
jahongashtamcjahongashtamc/hallwright/.agents/skills/reverse-engineer-anything/SKILL.md

reverse-engineer-anything

Skill1 starsChanged 13 days agoMITView on GitHub

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 clean-room reconstruction.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when investigating a shipped binary, packaged application, decompiled code, passive application runtime evidence, or …

    line 10
  2. Very specific:

    Look for entry points in package.json, main processes (main.js / background.js), preload scripts, and IPC communication channels …

    line 28
  3. Distinctive:

    Use Ghidra or Hopper headless scripts to generate pseudocode for critical dispatch routines.

    line 33
  4. Distinctive:

    Catalog Interface Contracts: Document all endpoints, parameters, JSON models, and state transitions.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reverse Engineer Anything (REA)

Use this skill when investigating a shipped binary, packaged application, decompiled code, passive application runtime evidence, or reconstructing features from compiled software.

1. Principles of Reverse Engineering

  • Evidence-First Analysis: Ground every conclusion in factual decompiled symbols, strings, and cross-references. Never guess how a compiled binary or minified bundle works.
  • Clean-Room Reconstruction: Distinguish between observed implementation details and modern architectural recreation.
  • Safety & Isolation: Process binaries and archives in isolated directories; never execute untrusted targets outside controlled sandboxes.

2. Target Routing Playbook

JavaScript, Node.js & Electron Applications:

  • ASAR / Packed Archives: Extract .asar archives to examine plaintext sources, configuration manifests, and IPC handlers:
    npx -y asar extract /path/to/app.asar ./extracted_app
  • CLI Analysis via REA:
    npx -y rea-agents@latest analyze-javascript-application /path/to/extracted --json
  • Look for entry points in package.json, main processes (main.js / background.js), preload scripts, and IPC communication channels (ipcRenderer.send, ipcMain.handle).

Native Binaries (PE, ELF, Mach-O):

  • Inspect headers, imported DLLs/shared libraries, and exported symbols.
  • Identify compiler toolchains (MSVC, GCC, Clang, Go, Rust, or .NET NativeAOT).
  • Use Ghidra or Hopper headless scripts to generate pseudocode for critical dispatch routines.

Mobile Applications (Android APK / iOS IPA):

  • Android APK: Unpack with apktool or decompile DEX to Java/Kotlin with JADX:
    jadx -d ./decompiled_apk target.apk
  • Analyze AndroidManifest.xml for exported activities, permissions, and network security configs.

Network & Web Traffic Traps:

  • Inspect HAR archives, Fiddler SAZ files, and WebSocket streams.
  • Reconstruct API request contracts, payload encryption schemes, and authentication handshakes.

3. Reconstruction Strategy

  1. Catalog Interface Contracts: Document all endpoints, parameters, JSON models, and state transitions.
  2. Isolate Core Algorithms: Extract mathematical formulas, hashing/checksum routines, and encoding algorithms.
  3. Re-implement in Modern Stack: Re-author cleanly in TypeScript, Python, or Go with 100% type coverage, comprehensive unit tests, and zero copyright contamination.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free