Pre-open-source Core Achievements (DeepSeek V4 Flash Driven)

Before the project was open-sourced, I used https://github.com/zhaoxuya520/reverse-skill… to complete multiple high-difficulty reverse engineering and security research tasks, fully validating the model’s powerful capabilities in real-world complex engineering scenarios:

• High-quality disassembly of a Go-compiled EXE in 5 minutes: Quickly restored a PC executable compiled with Go and stripped of symbol tables into a nearly readable source code structure, greatly lowering the barrier to reverse engineering analysis.
• One-click decompilation of an Android APK: Successfully restored an APK to its pre-packaging engineering code state (Smali + resources + manifest and full structure), providing a clear original framework for subsequent analysis and modification.
• Zero-credential web backend intrusion: For a web application developed using GPT-5.5, rapidly located and exploited key vulnerabilities without any account information, directly accessing the management backend and verifying its security risks.

In addition, many other complex tasks were completed, including but not limited to: binary protocol reverse engineering, obfuscated code deobfuscation, encrypted communication traffic analysis, automated vulnerability mining, etc. There were also game security related contents, but I deleted them from the open-source version out of concern they might be used for cheating tools.

zhaoxuya520/reverse-skill

Source: https://github.com/zhaoxuya520/reverse-skill

Cybersecurity Skills Router / Reverse-Engineering Skill Routing Pack

An AI Agent workflow router and tool orchestration system for reverse engineering, security analysis, and CTF tasks.

Human readers: start with OVERVIEW.md. 中文概览: OVERVIEW_zh.md

AI Agents: do not open the overview by default. Continue to section 0 and execute the bootstrap flow.

This README is intentionally structured as an AI Agent bootstrap entry: execution rules come first so an Agent can configure itself and start routing tasks. If you only want to understand what the project does, read the human-friendly overview first.

AI Community: https://linux.do

This package can be placed in any directory. The AI will automatically detect its actual path. In the following text, <PackageRoot> refers to your real installation path.

0. First Instruction for the AI (Execute Immediately After Reading This README)

After the AI finishes reading this file, it must automatically execute the following configuration process and then report what was changed. The user does not need to operate manually. ⚠️ FIRST-TIME SETUP: skills/tool-index.md is gitignored and does NOT exist in the cloned repo until you generate it. Before reading RULES.md, you MUST first refresh the local tool index:

• Windows: powershell -ExecutionPolicy Bypass -File skills/scripts/refresh-tool-index.ps1
• Linux/macOS: bash skills/scripts/refresh-tool-index.sh
• Kali: bash kali/scripts/refresh-tool-index.sh This generates skills/tool-index.md and skills/tool-index.json for the current machine. Without this step, RULES.md will fail to read tool-index.md and routing will be broken.

Automatic Configuration Process

0. ⚠️ Run refresh-tool-index first to generate skills/tool-index.md (see warning above)
1. Detect the actual installation path of this package (derived from the location of this file, i.e., the directory containing README.md)
2. Detect the local operating system and distribution:
   - Windows → continue with this README and the PowerShell script path
   - Kali Linux → read kali/README-kali.md
   - Generic Linux (Ubuntu / Debian / Mint / Pop!_OS, etc.) → read docs/platforms/linux.md
   - macOS → read docs/platforms/macos.md
   - Other / unknown → read PLATFORMS.md and choose the closest deployment path
3. Follow the platform-specific deployment document to check toolchains, script entry points, MCP configuration, and path conventions
4. If the current system supports Bash, prefer the parity bootstrap entry: bash skills/scripts/bootstrap-reverse.sh ; for index refresh only, run: bash skills/scripts/refresh-tool-index.sh
5. Read RULES.md → execute all instructions inside it (including the CRITICAL immediate-action block, global injection, precedent-file reading, and routing)
6. Continue executing the complete behavior chain in RULES.md → enter the corresponding skill → start working

Platform deployment routing table

RULES.md contains the full behavior chain (steps 0–14). After reading this README, first complete OS detection and platform-document routing, then read RULES.md and start executing. Do not stop at “configuration completed.“ The configuration report can be output after platform detection and RULES.md loading, but it is not the endpoint—the endpoint is the user’s task being actually completed.

Example Report Format

✅ **Reverse-Engineering Skill Routing Pack Configured Successfully**
**Installation path**: C:\Users\xxx\Desktop\reverse-skill-private-main
**System detected**: Windows / Kali Linux / generic Linux / macOS / other
**Deployment document**: <path>
**Tool status**:
- Available: node, python, pip, ...
- Missing (auto-install when needed): jadx, radare2, ...
- Missing (manual installation required): zipalign, apksigner, IDA Pro
**Tool index**: <path>
**Rules written to**: <path> (part of the system behavior chain)
**Note**: Future reverse-engineering / penetration-testing / security tasks will be routed automatically. Missing tools will be installed automatically when needed.

This is not a “single-tool installer.” It is a security-task Skill Router for code Agents such as Claude Code, Codex CLI, Cursor, Cline, and Windsurf: classify the task, enter the right workflow, then call real tools to execute. It solves two problems:

1. When the AI encounters APK / binary / frontend JS / packet-capture / CTF tasks, it routes to the right methodology and sub-skill before touching tools.
2. It consolidates local tools, MCP servers, script entry points, and workflows into a reusable asset that can move cleanly across machines.

Platform support

Generic Linux/macOS users can list bootstrap capabilities with:

bash skills/scripts/bootstrap-reverse.sh --list

Kali users should use the dedicated Kali entrypoint:

bash kali/scripts/bootstrap-reverse.sh

For index refresh only, run:

bash skills/scripts/refresh-tool-index.sh

See PLATFORMS.md for the full support matrix.

1. What Is Included in This Package

At present, it is recommended to understand the whole package as two layers:

<PackageRoot>
├── Readme.md                 # The installation/distribution guide you are reading now
├── CTF-Sandbox-Orchestrator\  # Full CTF competition stack (40+ sub-skills)
└── skills\                    # Main skills directory
    ├── SKILL.md               # Main controller entry point
    ├── routing.md             # Scenario → skill dispatching (routing matrix)
    ├── CONTRIBUTING.md        # Guide for adding new skills
    ├── tool-index.md          # Tool index (auto-generated)
    ├── scripts\               # Tool-index refresh and shared scripts
    ├── field-journal\         # Auto-evolving experience logs
    ├── apk-reverse\           # APK reverse engineering
    ├── attack-chain\          # Multi-stage attack-chain orchestration
    ├── binary-diff\           # Cross-version symbol migration
    ├── browser-automation\    # Browser + desktop automation (Playwright + OpenReverse)
    ├── diagram-generator\     # Diagram generation (Mermaid / Graphviz / PlantUML)
    ├── docs-generator\        # Technical document/report generation
    ├── edr-bypass-re\         # EDR bypass reverse engineering (red-team delivery)
    ├── firmware-pentest\      # Firmware penetration-testing chain (OWASP FSTM)
    ├── ida-reverse\           # IDA Pro reverse engineering
    ├── js-reverse\            # Frontend JS / browser-chain reverse engineering
    ├── patch-diff-exploit\    # N-day patch diff → exploitation
    ├── pentest-tools\         # Penetration-testing toolchain
    ├── pwn-chain\             # RE → usable exploit (stack / heap / kernel)
    ├── radare2\               # radare2 CLI reverse engineering
    └── reverse-engineering\   # General reverse-engineering methodology

If you also use the CTF knowledge base, it is recommended to place it under the root of this package (the current default structure):

<PackageRoot>
├── skills\                    # Main skills directory
├── CTF-Sandbox-Orchestrator\  # CTF competition sub-skills (40+)
└── Readme.md

This allows the relative paths in routing.md, such as ../CTF-Sandbox-Orchestrator/..., to resolve correctly from skills/.

If you place CTF-Sandbox-Orchestrator outside this package, such as F:\CTF-Sandbox-Orchestrator\, you need to manually adjust the relative paths in routing.md.

2. Recommended Installation Approach

2.1 Recommended Directory Layout

After downloading, users are recommended to place the package as follows:

<PackageRoot>                 # Package root; drive letter can be changed
<OtherTools>                  # Various tool paths, e.g.:
    C:\Users\<User>\Tools\jadx\
    C:\Users\<User>\Tools\apktool\
    C:\Users\<User>\AppData\Local\Android\Sdk\platform-tools\
    C:\Users\<User>\AppData\Local\Programs\Python\Python3xx\
    C:\Program Files\nodejs\
    D:\APP\IDA\               # Example only; customize as needed
    C:\Tools\radare2\         # Optional

2.2 Do Not Treat These Values as Hard Requirements

Many scripts, documents, and tool indexes in this package contain sample paths. These paths only represent one machine’s layout. They do not mean that you must copy them exactly. After migrating to a new machine, especially check paths such as:

• D:\APP\IDA
• <PackageRoot>\...
• <User>\...

If you change drive letters, usernames, or tool installation directories, adjust them according to the “Required Changes After Migration“ section in this document.

3. Quick Start

3.1 If You Only Want to Put the Skill Pack in Place First

1. Put the whole directory somewhere you like, for example: <PackageRoot>
2. Go to skills\SKILL.md
3. When handling a task, read files in this order:
   1. SKILL.md
   2. routing.md
   3. The SKILL.md in the corresponding subdirectory
4. Read tool-index.md only when you need to confirm local tools

3.2 If You Want Any Code CLI to Automatically Use This Routing

You need at least:

• A code CLI that supports custom rules / system prompts / project instructions / hooks
• A way to inject “read the routing file first for reverse-engineering tasks“ into the model context
• If direct external capabilities are needed, configure MCP or an equivalent tool bridge
• This package’s SKILL.md, routing.md, and tool-index.md

If you already have Claude hooks, Codex CLI project instructions, Cursor Rules, Cline custom instructions, or Windsurf Rules, update any old paths inside them to the current installation path.

4. Dependency Table: What to Install, Where to Download, and Where to Put It

The following tables are grouped by “required / commonly used / optional enhancement.“

4.1 Core Clients and Runtimes

4.2 APK / Android Reverse-Engineering Tools

4.3 Dynamic Analysis and Browser-Side Tools

4.4 Binary Reverse-Engineering Tools

4.5 Supporting Knowledge Base

5. Supported Scenarios by Default

5.1 Main Modules Under skills\