What Are the Different Modules or Components of reverse-skill?

reverse-skill is organized as a skill-router with six core component types: routing logic, operational contracts, automation scripts, domain-specific skill modules, documentation, and platform-specific tooling.

This repository by zhaoxuya520/reverse-skill implements a decision-driven architecture for security workflows. Each component handles a distinct phase—from initial task classification to final execution—making it suitable for reverse-engineering, penetration testing, and CTF operations.

Core Routing System

The core routing component defines how tasks are classified and dispatched. It lives primarily in skills/MASTER-ROUTING.md, skills/routing.md, skills/SKILL.md, and the global RULES.md.

These files establish the MASTER-ROUTING ladder—a priority-ordered decision tree that matches user intent against target type and available toolchain. The routing matrix in skills/routing.md provides the full mapping, while RULES.md enforces guardrails like "route before act."

# Execute the primary routing ladder

powershell -File skills/scripts/master-route.ps1 -Task "decompile this apk and look for hidden URLs"

This script consumes MASTER-ROUTING.md and outputs the appropriate skill directory path.

Ops Contracts

Located in skills/ops/, the ops contracts standardize workflow metadata. These include:

• Scope contracts—boundary definitions for engagement
• Evidence-to-finding pipelines—traceability from raw data to conclusions
• Role maps—responsibility assignments
• Timeline and work-item templates—structured task tracking
• Identity definitions—attribution and attribution boundaries

Initialized via skills/scripts/case-init.ps1:

# Create a new case workspace with all ops contracts

powershell -File skills/scripts/case-init.ps1 -CaseName "sample-apk-analysis"

This populates work/<case>/ with scope.md, timeline, and workitem templates before any ACT step executes.

Automation Scripts

The skills/scripts/ directory contains utility scripts that implement routing decisions and maintain workspace integrity:

Script	Purpose
master-route.ps1	Executes the primary routing ladder
case-init.ps1	Bootstraps case workspaces with ops contracts
refresh-tool-index.sh	Regenerates the local tool inventory

These bridge the routing logic with concrete filesystem operations.

Domain-Specific Skill Modules

Each subdirectory under skills/ implements a concrete workflow for a target type or technique. The primary modules include:

Mobile Reverse Engineering

• APK/Android reverse (skills/apk-reverse/)—Decompilation, unpacking, re-signing, and Frida hook integration
• iOS reverse (skills/mobile-reverse/)—Class-dump, Hopper workflows, Frida iOS, and IPA analysis

Binary Analysis

• IDA reverse (skills/ida-reverse/)—IDA Pro MCP workflows, static decompilation, and plugin orchestration
• Radare2 reverse (skills/radare2/)—CLI-driven analysis and recon scripts

Web and Frontend

• JS/frontend reverse (skills/js-reverse/)—Observer pattern implementation, encrypted logic capture, and reconstruction

General Reverse Engineering

• Reverse-engineering core (skills/reverse-engineering/)—OLLVM deobfuscation, language-specific guides, and dynamic analysis helpers

Offensive Security

• Pentest tools (skills/pentest-tools/)—Port scanning, vulnerability detection, password cracking, and automated MCP suites
• Attack-chain orchestration (skills/attack-chain/)—End-to-end red-team pipelines, C2 frameworks, and post-exploitation planning

Specialized Domains

• CTF-Sandbox Orchestrator (CTF-Sandbox-Orchestrator/)—Aggregates 40+ sub-skills for competition environments
• Diagram generator (skills/diagram-generator/)—Mermaid, GraphViz, and PlantUML rendering for attack paths and reports

Additional Coverage

Extended modules cover Wi-Fi/wireless (skills/wifi-wireless/), radio/SDR (skills/radio-sdr/), threat-hunting, thick-client analysis, identity federation, supply-chain security, and LLM security.

Documentation and Tooling

Documentation

• README.md—Project overview and quick-start matrix
• docs/ARCHITECTURE.md—Visual and textual architecture description
• Platform-specific integration guides

Platform-Specific Tooling

• kali/scripts/—Bash helpers for Kali Linux installation and toolset management
• skills/tool-index.md—Auto-generated snapshot of locally available tools with paths and versions

Tool Index and Maintenance

The skills/tool-index.md file provides a machine-readable inventory of the execution environment. Updated via refresh-tool-index.sh, it enables scripts to validate toolchain availability before routing.

Summary

reverse-skill's modular architecture comprises:

• Routing logic—MASTER-ROUTING ladder and decision matrices
• Operational contracts—Standardized scope, evidence, and timeline handling
• Automation scripts—PowerShell and Bash implementations of routing decisions
• Domain-specific skill modules—Targeted workflows for APK, iOS, IDA, Radare2, JavaScript, pentest, attack-chain, CTF, and specialized domains
• Support documentation——README, architecture diagrams, and platform guides
• Platform tooling—Kali-specific scripts and auto-generated tool indices

Frequently Asked Questions

How does the routing system decide which skill module to use?

The routing system in skills/MASTER-ROUTING.md applies a priority-ordered ladder that examines task description keywords, target type (APK, IPA, ELF, etc.), and available toolchain. The master-route.ps1 script implements this logic, cross-referencing skills/routing.md for the full matrix of alternatives. Output is a filesystem path to the appropriate skill directory.

What is the purpose of the ops contracts in skills/ops/?

Ops contracts enforce consistency across engagements by defining scope boundaries, evidence handling pipelines, role assignments, and work-item structures. Created via case-init.ps1, they ensure that routed skills operate within documented constraints with full traceability from raw data to findings.

Can the CTF-Sandbox-Orchestrator run independently of other modules?

Yes. The CTF-Sandbox-Orchestrator/ directory contains a self-contained competition environment that aggregates 40+ sub-skills. While it references the same routing conventions, it includes its own orchestration logic for sandbox lifecycle management and challenge-specific toolchains.

How is the tool index kept synchronized with the local environment?

The skills/scripts/refresh-tool-index.sh script (with Kali variant at kali/scripts/refresh-tool-index.sh) scans the filesystem for installed security tools, capturing paths and versions into skills/tool-index.md. Routing scripts reference this index to validate prerequisites before dispatching tasks to specific skill modules.

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