zhaoxuya520 / reverse-skill

Skills router for coding agents

The agent has the tools.
It does not know which one.

When an agent meets an APK, a binary, encrypted frontend JS, a CTF challenge or an authorized pentest target, this package routes it to the right methodology, checks the available tools, and executes a repeatable workflow instead of guessing commands. Client-neutral: Claude Code, Codex, Cursor, OpenCode and other compatible clients.

Read the source The routing ladder

Current status, as published

44routing rules (R0–R45)
175regression benchmark cases
45tracked core skill modules
Windows + UbuntuCI platforms

Figures are the project’s own published status table, reproduced as stated. A router with a regression suite is a router you can argue with.

The ladder

one cell is a gate, not a step
Arrive
Rules
Route
Gate
Record
01 User task An APK, an ELF, frontend JS, a PCAP, a CTF challenge.
02 RULES.md The constraints are read before anything is chosen.
03 MASTER-ROUTING The primary ladder picks the scenario skill, then the tools, MCP servers and scripts.
04 case-init · scope.md Authorisation and network profile are established. No target action until ready.
05 Timeline → report Evidence, finding, path — then the report and the field journal.

Why a router

Agents don’t know whether to reach for jadx, apktool, Frida, IDA or BurpSuite on a given task. APK, ELF, JS, PCAP and CTF each need a different playbook.

Why one config

The routing core is driven by one structured configuration, validated by cross-platform CI and kept separate from optional client adapters.

Why a field journal

Because otherwise the same mistakes get repeated — the project’s own words for experience that never gets reused.