android-reverse-engineering-skill — What is it?

SimoneAvogadro/android-reverse-engineering-skill is a Claude Code skill designed to decompile Android applications and extract HTTP APIs, enabling reverse engineering without the original source code.

⭐ 5,287 Stars 🍴 598 Forks Shell Apache-2.0 Author: SimoneAvogadro
Source: README View on GitHub →

Why it matters

This project is gaining attention due to its specialized focus on Android reverse engineering, addressing the need for analyzing apps without source code. Its integration with Claude Code and support for various decompilation tools make it a unique tool for security researchers and developers.

Source: README, project traits

Core Features

Decompile APKs

Supports decompilation of APK, XAPK, JAR, and AAR files using jadx and Fernflower/Vineflower, with options for single engine or side-by-side comparison.

Source: README
Extract APIs

Extracts HTTP APIs, including Retrofit endpoints, OkHttp calls, hardcoded URLs, and authentication patterns.

Source: README
Trace Call Flows

Traces call flows from Activities/Fragments through ViewModels and repositories down to HTTP calls, aiding in understanding the app's architecture.

Source: README
Analyze Structure

Analyzes the app's manifest, packages, and architecture patterns, providing insights into the app's design.

Source: README
Handle Obfuscation

Implements strategies for navigating ProGuard/R8 obfuscation, making it easier to work with obfuscated code.

Source: README

Architecture

The architecture is modular, with separate scripts for dependency checking, installation, decompilation, and API extraction. It leverages Claude Code's plugin system and utilizes various decompilation tools like jadx and Fernflower/Vineflower. The code is organized into a clear directory structure, with scripts and documentation for each component.

Source: Code tree

Project Knowledge Graph

Knowledge graph: project (center) + core features (inner hexagons) + key dependencies (outer chips) jadx Fernflower/VineflowerFernflower/Vin… dex2jar Decompile APKs Extract APIs Trace Call Flows Analyze Structure Handle Obfuscation android-reverse-engi… Project Core feature Key dependency

Center: project; inner ring: core feature modules; outer ring: key dependencies. Auto-generated from core_features and tech_stack.key_deps.

Tech Stack

LanguageShellFrameworkClaude Code plugin system
jadxFernflower/Vineflowerdex2jar
Not specified
Source: README, code tree

Quick Start

From GitHub: /plugin marketplace add SimoneAvogadro/android-reverse-engineering-skill /plugin install android-reverse-engineering@android-reverse-engineering-skill From local clone: git clone https://github.com/SimoneAvogadro/android-reverse-engineering-skill.git /plugin marketplace add /path/to/android-reverse-engineering-skill /plugin install android-reverse-engineering@android-reverse-engineering-skill
Source: README Installation/Quick Start

Use Cases

This project is for security researchers, developers, and anyone needing to analyze Android applications without source code. It is useful for reverse engineering apps, analyzing security vulnerabilities, and understanding app architecture.

Source: README

Strengths & Limitations

Strengths

  • Strength 1: Specialized in Android reverse engineering
  • Strength 2: Integrates with Claude Code for seamless usage
  • Strength 3: Supports multiple decompilation tools

Limitations

  • Limitation 1: Limited to Android applications
  • Limitation 2: Experimental support for Windows/Powershell
Source: README, code structure

Latest Release

v1.1.0 (2026-04-27): Added Chinese localization.

Source: GitHub Releases

Verdict

SimoneAvogadro/android-reverse-engineering-skill is a valuable tool for those involved in Android app analysis, offering specialized features and integration with Claude Code. It is particularly suited for security researchers and developers who require in-depth analysis of Android applications without source code.

Source: Synthesis
Transparency Notice
This page is auto-generated by AI (a large language model) from the following public materials: GitHub README, code tree, dependency files and release notes. Analyzed at: 2026-05-22 21:21. Quality score: 85/100.

Data sources: README, GitHub API, dependency files