Reverse Engineer Anything
A companion instruction for investigating shipped apps and binaries with the separately configured REA tools.
morluto is the creator behind REA, a tool that helps coding agents investigate how software works. Explore REA, flameox, and focused Skills for reverse engineering and repository previews, with direct links to project documentation, examples, and the creator’s public work.
morluto is a developer and applied researcher whose public work combines open-source software, agents, and practical investigations. The personal blog is a place for notes on reading and building; the GitHub profile describes research interests in agents, reinforcement-learning environments, and preference learning.
REA, short for Reverse Engineer Anything, helps coding agents investigate applications and native binaries. Its website presents examples of tracing software behavior and reconstructing individual features. flameox addresses a different question: finding performance costs through profiling and runtime evidence. Both projects connect engineering questions with inspectable evidence.
The published Skills support narrower workflows within that wider body of work. Reverse Engineer Anything provides instructions associated with REA, while Generate Social Preview turns a project’s purpose and visual references into a sharing image. Choosing an instruction is separate from installing the supporting tool or checking the results it produces.
Choose between instructions for investigating shipped software and creating a repository social preview. Each entry addresses a distinct task; read its original SKILL.md for the workflow, required tools, and inputs before deciding how it fits the work.
A companion instruction for investigating shipped apps and binaries with the separately configured REA tools.
An instruction for creating repository social previews from the project's purpose and visual references.
REA and flameox are software projects with different engineering goals: investigating application behavior and finding performance costs. Follow their repositories for current setup and implementation details, rather than treating a companion Skill as the tool itself or assuming shared prerequisites.
Explore other people and teams working on agent instructions, developer tools, and interface workflows. Compare the purpose of each project and the evidence behind its guidance, then open the relevant publisher profile to understand the source of the work.
Start with the task: investigate software behavior or prepare a project’s social preview. Review the matching instructions, gather the required inputs, and verify the supporting tools before running the workflow or relying on its results.