Skip to content
SkillModel-led688 tokens in use

competition-reverse-pwn

A CTF sandbox workflow for reverse engineering, malware triage, DFIR and native exploit challenges, with routing to narrower skills.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-reverse-pwn
git clone https://github.com/zhaoxuya520/reverse-skill.git
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing competition-reverse-pwn costs

107tokens idle
688tokens in use
900tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure25/25
  • Examples0/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a downstream specialization of the ctf-sandbox-orchestrator skill. It covers binary-heavy CTF challenges: reversing a sample, unpacking layers, inspecting memory dumps or captures, debugging crashes and verifying exploit primitives under sandbox assumptions.

It starts with passive triage (type, headers, sections, imports, strings, entropy), preserves the original artifact, keeps decoded and instrumented copies separate and ties each claim to an observable boundary. It routes to sibling skills for malware config, firmware, file parsers, PCAP and timelines. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A passive triage order for headers, sections, imports, strings, entropy and resources
  • A native path checklist covering mitigations, loader, libc build, syscall surface and protocol framing
  • Rules for keeping original, decoded, dumped and instrumented artifacts as separate files
  • A routing list to eight narrower sibling skills

Common Use Cases

  • Triaging a suspicious binary in a CTF reverse challenge
  • Recording crash state and leak sources while verifying an exploit primitive in a lab
  • Correlating files, registry, services and captures into one execution graph for a DFIR challenge

What Makes It Unique

It spans reverse, DFIR and pwn work in one entry point and then routes to narrower skills for malware config, firmware, parsers, source maps, container escape, PCAP, custom protocols and timelines. It requires replaying a primitive from a clean baseline before naming it, and it runs only after the orchestrator skill has set sandbox assumptions.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference playbook and an agent config file that disables implicit invocation. It ships no scripts and does not itself fetch pages, call APIs, run commands or write files. Triage and debugging use the reverse engineering tools the user already has in the sandbox.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers