Reverse Skill
zhaoxuya520/reverse-skill
A router pack that points your coding agent at the right reverse-engineering or security workflow instead of guessing commands.
GitHub repository
Overview
Think of this as a map for security research work. When you drop an APK, a binary, or a CTF challenge into Claude Code / Cursor, Reverse Skill routes the job to the matching playbook (APK reverse, IDA, JS signing, malware, and more) and checks which local tools you already have. Repo (copy/paste): https://github.com/zhaoxuya520/reverse-skill Only use on systems you are authorized to test.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Not installed into LimeDock.
1. Copy: https://github.com/zhaoxuya520/reverse-skill 2. Clone the repo locally. 3. Point your coding agent at RULES.md / README_AI.md so it loads the router. 4. Confirm your local tools (jadx, IDA, Frida, etc.) before a real case.
How to use it
**Simple example** You have an Android APK you are allowed to analyze.
1. Open the repo in your agent. 2. Say: “Route this APK — unpack, decompile, find the login signing.” 3. The router picks `apk-reverse` / related skills and walks a repeatable workflow. 4. You get structured steps + a report instead of random shell guesses.
Example prompts
- “Read RULES.md, then route this authorized APK analysis end to end.”
- “Which reverse-skill module should I use for frontend JS signing?”
- “Start a case folder with scope, timeline, and tool checklist for this binary.”
Use cases and examples
- Authorized APK / mobile reverse work
- CTF challenge routing
- Binary analysis with a checklist, not vibes
- JS frontend signing / request replay research
Prerequisites
- Coding agent that can read repo rules (Claude Code, Cursor, Cline, etc.)
- Local reverse / security tools for the modules you need
- Written authorization for any real target
Tips
- Treat this as a router + playbooks — not a one-click exploit kit.
- Start with MASTER-ROUTING.md when you are unsure which module fits.
- Keep scope and evidence notes before you ACT.