android-reverse-engineering is a skill for analyzing Android packages. It fingerprints an app first to see which framework and HTTP stack it uses, decompiles it with jadx or Fernflower and Vineflower, and then works through the structure, call flows and API calls.
The result is an architecture summary, a table of endpoints with host, method, path, authentication and source file, and deeper notes on the endpoints that matter, such as login and payment. The README states that the tool is for lawful purposes such as security research with authorization, interoperability analysis, malware analysis and CTF competitions.
What You Get
- Decompiled sources in an output folder, from jadx, Fernflower or Vineflower or both for comparison
- An architecture summary of the app’s structure and patterns
- A table of discovered endpoints with host, method, path, authentication and source file
- Deeper notes for high-value endpoints such as login and payment flows
- A call flow map from activities down to the network layer
- Scripts for Bash and PowerShell that can also be run on their own
Common Use Cases
- Documenting the backend API of an app you are permitted to analyze
- Reading obfuscated Kotlin code with recovered original class names
- Checking a library in JAR or AAR form for how it makes network calls
- Triage of an APK to decide whether decompiling Java code is worthwhile
What Makes It Unique
It starts with a fingerprint step that avoids wasted decompiling on apps whose real code is not Java or Kotlin, and it recovers original Kotlin class names from metadata that obfuscation leaves in place. Its API search covers Retrofit, OkHttp, Volley, Ktor and Apollo, and its output is a two-tier format that keeps the long notes for the endpoints that need them.
Under The Hood
The skill runs bundled Bash and PowerShell scripts on the package you point it at. These scripts check for Java, jadx and optional tools, then can install missing ones: they query GitHub for the latest release, download archives or jars, unpack them into a folder in the user’s home, add a path line to the shell profile and may call the system package manager with sudo. Other scripts run the decompilers, scan the output for URLs and API annotations, and write mapping files and output folders. The instructions also tell the agent to read the decompiled files and write documentation. The PowerShell versions of the scripts could not be read by the directory’s scanner, so what they do is not described or scored here. The README states that the plugin is for lawful use such as authorized security research, interoperability analysis, malware analysis and CTF competitions.