reverse-skill
reverse-skill: quickstart para enrutar un caso autorizado
De RULES y MASTER-ROUTING al índice de herramientas, case-init, evidencia y entrega.
Qué aprenderás
- Initialize an authorized reverse-skill case
- Use routing and tool-index evidence
- Produce a replayable handoff
Antes de empezar
- Basic Git and command-line usage
- Comfort reading a project README
You can explain the project, run its documented first step, and decide what to verify before adopting it.
Conclusiones clave
- Authorization and scope gates precede any active security action.
- Routing rules and tool index make methodology selection reproducible.
- Evidence hashes, timelines, and bounded handoffs turn tool output into reviewable findings.
Start with scope, not commands
Define autorización, alcance y network_profile, actualiza el índice y ejecuta la ruta principal. Usa una fixture propia o CTF para crear scope, timeline, Evidence/Finding/Path y un informe redactado.
Use a disposable local case with a sample you own or a public CTF fixture. Keep the repository revision, case identifier, authorization note, target hash, and intended output in the run card before refreshing the tool index.
Refresh tools and choose a route
Install the repository, run the platform-specific tool-index refresh, and inspect `skills/tool-index.md`. The matrix distinguishes jadx/apktool, Frida, IDA/radare2/Ghidra, Burp/Reqable, YARA, nmap, and other tools; availability is evidence, not permission.
Run the master route against a plain-language task and record the selected R0–R44 rule, required tools, and skipped branches. If the hint is ambiguous, stop for human clarification rather than guessing a high-impact workflow.
Capture evidence as you work
Initialize `scope.md`, timeline, workitems, and a field journal. Every observation should carry a source path, command or tool, timestamp, artifact hash, and analyst note. Separate Evidence, Finding, and Path so a hypothesis cannot silently become a confirmed vulnerability.
Prefer read-only inspection first. Keep network access disabled or allow-listed until the case contract permits it, and never place credentials or real personal data in a fixture or report example.
Finish with a bounded handoff
Use case-review and docs-generator paths to produce a report that states scope, methods, evidence, limitations, remediation, and retest criteria. Run the documented routing regression and coherence checks after changing rules or manifests.
The quickstart is successful when another authorized reviewer can replay the route and locate every claim in a hashed artifact—not when a tool prints an impressive output.
Cómo elegir
| Criterio | Opción A | Opción B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Pasos de implementación
- 1
Pin the repository and create an authorized disposable case.
- 2
Refresh the platform tool index and run the master route.
- 3
Record scope, evidence, hashes, findings, and network decisions.
- 4
Run regression/coherence checks and produce a redacted handoff report.
Ejemplo para copiar
git clone https://github.com/zhaoxuya520/reverse-skill.git
cd reverse-skill
powershell -File skills/scripts/refresh-tool-index.ps1
powershell -File skills/scripts/master-route.ps1 -Hint "analyze my APK fixture"
powershell -File skills/scripts/case-init.ps1 -CaseId demo-apkPreguntas frecuentes
Can I use reverse-skill against an unknown public target?
No. Use only systems, samples, or CTF targets you own or have explicit authorization to assess.
What if the route is ambiguous?
Pause for scope clarification and record the decision; do not guess a high-impact tool chain.
Fuentes
- reverse-skill README (captured 2026-08-31)Fuente verificada 2026-08-31
- reverse-skill repositoryFuente verificada 2026-08-31