agentleFS
2233admin2233admin/reverse-skill-evolver/SKILL.md

reverse-skill-evolver

Skill26 starsChanged 10 days agoMITView on GitHub

Route authorized reverse-engineering, cybersecurity, and CTF tasks through the bundled skills and tool workflows. Use for APK/mobile, native binaries, JavaScript signatures, captured protocols, security assessments, Forefy ASR discovery, and bounded routing evolution.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the directory intact when installing or updating it.

    line 10
  2. Distinctive:

    Read and execute referenced module files in this installed package.

    line 20
  3. Very specific:

    Use the current task's inputs, authorization, requested output, and success checks to select a route.

    line 26
  4. Very specific:

    Read skills/routing.json and skills/routing.md, then the selected module's SKILL.md.

    line 29
  5. Very specific:

    Use the bundled launcher whenever a module needs reverse-skill:

    line 46
  6. Very specific:

    Create an explicit case record with case init --hint "<task>" --case-name NAME --package-root "<workspace>".

    line 66
  7. Very specific:

    Use skills/case-review/SKILL.md for scope, evidence links, timeline and artifact hash review.

    line 69
  8. Very specific:

    Use gates all to check repository versions, CLI descriptions and routing paths.

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reverse Skill Evolver

This directory is one complete installable skill. Its skills/ and CTF-Sandbox-Orchestrator/ directories are bundled modules and resources. Keep the directory intact when installing or updating it.

Locate the package

Resolve paths from this SKILL.md, regardless of the caller's working directory:

  • <PACK_ROOT>: the directory containing this file.
  • <SKILL_ROOT>: <PACK_ROOT>/skills.
  • CTF modules: <PACK_ROOT>/CTF-Sandbox-Orchestrator.

Read and execute referenced module files in this installed package. Their relative paths depend on the bundled layout. Client registration is handled by the skill installer; using this skill does not require global rule injection.

Route the task

  1. Use the current task's inputs, authorization, requested output, and success checks to select a route. For multi-step work, use skills/evolution/goal.template.yaml and skills/evolution/SKILL.md.
  2. Read skills/routing.json and skills/routing.md, then the selected module's SKILL.md. An explicit Forefy ASR request enters skills/asr-registry/SKILL.md. For a deterministic suggestion, run python "<PACK_ROOT>/scripts/run.py" --json route "<task>". selected reports a route recommendation; tool availability and the current task's authorization still need verification before executing the workflow.
  3. Consult skills/ROUTER.md for shared tool discovery, bootstrap, reporting, and journal conventions when those parts of the workflow apply. Tool availability and external service configuration are separate from installing this bundle.
  4. Execute the requested workflow within the current authorization. Preserve evidence for results and route changes. Apply the evolution promotion gate to learned changes before treating them as stable routing knowledge.

Python CLI

Use the bundled launcher whenever a module needs reverse-skill:

python "<PACK_ROOT>/scripts/run.py" --help
python "<PACK_ROOT>/scripts/run.py" --json asr list

Python 3.10+ is required. On first use, the launcher creates a private runtime in the user's cache and installs this package and its declared dependencies. It preserves the caller's working directory, arguments, JSON output, and exit code, with UTF-8 output and imports isolated from the caller's Python environment. Setup diagnostics go to stderr. A setup failure stops before the CLI operation runs and reports the actual error.

For PowerShell, shell, and module-local helpers, use their bundled paths as documented by the selected module. Native tools and MCP services are prepared only when the requested workflow needs them.

Case records and optional project index

Create an explicit case record with case init --hint "<task>" --case-name NAME --package-root "<workspace>". It records declared scope and network mode and creates work/NAME/; it does not execute an analysis or grant authorization. Use skills/case-review/SKILL.md for scope, evidence links, timeline and artifact hash review. JSON failures retain output-v1's data=null; their error message includes the diagnostic report.

For a large workspace, index build "<workspace>" returns a plan. Only --apply creates .reverse-skill/index/v1.sqlite3; index update follows the same rule. retrieve "<workspace>" "<query>" --mode bm25|tree|hybrid reads the existing local index. Indexing is optional and does not change skill selection. Use gates all to check repository versions, CLI descriptions and routing paths; gates leak-scan "<path>" explicitly scans selected files with redacted findings. All commands use the bundled launcher above.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.