APK Reverse Engineering Keywords in reverse-skill: Complete Routing Reference

TLDR: The reverse-skill repository uses specific routing keywords defined in skills/routing.md and skills/config/routing.json to trigger APK decompilation workflows, supporting both English and Chinese trigger phrases for tools like jadx, apktool, and Frida.

The reverse-skill framework automates Android application analysis through a keyword-driven routing system. Understanding these APK reverse engineering keywords is essential for navigating the decompilation pipeline and selecting appropriate tools for static and dynamic analysis. The repository maintains bilingual keyword support across its routing tables and skill definitions.

Primary APK Reverse Engineering Keywords

The routing table in skills/routing.md and its Chinese equivalent skills/routing_zh.md map user requests to the apk-reverse/ skill directory through specific trigger phrases. The JSON source of truth resides in skills/config/routing.json.

Core APK Identification Terms

The fundamental keyword trigger is "APK / Android app" in English or "APK / Android 应用" in Chinese. When the routing engine detects these terms in a user query, it activates the full reverse-engineering pipeline documented in skills/apk-reverse/SKILL.md. This initiates the standard workflow: decode with apktool, decompile with jadx, and prepare for analysis.

Security Testing and Modification Keywords

For security assessments, the keyword "APK security testing / mobile security" routes to skills/apk-reverse/references/apk-security-checklist.md, implementing the OWASP MASTG (Mobile Application Security Testing Guide) checklist for systematic vulnerability analysis.

Modification workflows trigger on Chinese phrases "去除校验 / 解锁功能 / 绕过检测 / 去掉限制" (remove verification / unlock features / bypass detection / remove restrictions). These keywords initiate patch proposal workflows that locate check routines, document bypass strategies, and fall back to reverse-engineering/ when necessary.

Workflow Stage Keywords

Specific operational keywords trigger distinct pipeline stages:

• "APK unpack / repack / modify smali" — Triggers the decode → rebuild → sign → install sequence using apktool for smali manipulation
• "APK reverse path" or "APK 逆向路径" — Initiates the complete flow covering decode, static analysis, Frida hooking, native .so analysis, and rebuild
• "JEB / JEB Pro" — Routes to licensed cross-validation workflows for native ARM code analysis, distinct from open-source alternatives

Toolchain Keywords and Execution Triggers

Once the routing engine matches a keyword, the apk-reverse skill invokes specific tool actions defined in skills/apk-reverse/SKILL.md:

• apktool — Unpacks and repacks APK archives, enabling direct smali file modification
• jadx — Decompiles DEX bytecode to Java-like source for static analysis
• JEB Pro — Performs optional licensed cross-validation for native .so libraries and advanced decompilation
• Frida / Objection — Executes dynamic instrumentation and anti-debug bypasses
• rebuild-sign-install — Repackages modified APKs, signs them with debug certificates, and installs to connected devices

Routing Implementation in Source Code

The keyword-to-skill mapping logic is implemented in skills/config/routing.json. When the master routing script processes a hint containing APK-related keywords, it selects the appropriate skill and delegates to specific PowerShell or Bash scripts.

Example routing invocation:

# Matches the "APK / Android app" keyword

bash skills/scripts/master-route.sh --hint "APK reverse engineering of com.example.app"

This triggers the decode script in the skill directory:

pwsh -File "apk-reverse/scripts/decode.ps1" -ApkPath "com.example.app.apk"

The routing engine prioritizes exact keyword matches, falling back to partial matching for variants like "Android app" when the full "APK" term is absent but context suggests mobile reverse engineering.

Summary

• The primary routing tables in skills/routing.md and skills/routing_zh.md define bilingual keywords that trigger APK analysis workflows
• "APK / Android app" serves as the main entry point for decompilation tasks, routing to skills/apk-reverse/SKILL.md
• Security-focused keywords route to the OWASP MASTG checklist in apk-security-checklist.md
• Modification keywords like "去除校验" (remove verification) trigger patch proposal workflows
• Tool-specific execution flows invoke jadx, apktool, and Frida based on the matched keyword context
• The JSON routing configuration in skills/config/routing.json provides the definitive keyword-to-skill mapping

Frequently Asked Questions

What files contain the APK reverse engineering keywords in reverse-skill?

The keywords are documented in skills/routing.md (English) and skills/routing_zh.md (Chinese), with the machine-readable routing logic stored in skills/config/routing.json. The detailed skill implementation and tool invocations reside in skills/apk-reverse/SKILL.md.

How do Chinese keywords differ from English keywords in the routing system?

The routing system supports bilingual triggers with functional parity. For example, "APK / Android 应用" (Chinese) functions identically to "APK / Android app" (English), routing to the same apk-reverse/ skill directory and tooling pipeline without requiring English input.

What happens when I use the "APK security testing" keyword?

This keyword routes to skills/apk-reverse/references/apk-security-checklist.md, which loads the OWASP MASTG checklist for systematic security assessment. This path emphasizes vulnerability discovery over general decompilation, though it may still invoke jadx and apktool for code review.

Can I trigger specific tools like JEB Pro using keywords?

Yes. The keyword "JEB / JEB Pro" specifically routes to licensed analysis workflows for native ARM code cross-validation. This bypasses the default open-source toolchain (jadx/apktool) triggered by general APK keywords, requiring valid JEB Pro licensing as noted in skills/apk-reverse/SKILL.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}