Skip to main content
skill CX Codex

competition-reverse-pwn — Claude Code skill: what it does

competition-reverse-pwn is a Claude Code skill for binary and vulnerability analysis in CTF challenges. After $ctf-sandbox-orchestrator is active, it inspects dumps and verifies exploit chains.

MIT 109 installs ★ 45,047 updated 2026-09-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaoxuya520/reverse-skill --skill competition-reverse-pwn -a claude-code
Open on GitHub

What competition-reverse-pwn does

The tool focuses on binary-heavy tasks involving artifact inspection, decoded layers, process behavior, and crash states. It maps mitigations, syscall surfaces, and protocol framing while keeping decoded or dumped artifacts separate from the original samples.

Ensure that $ctf-sandbox-orchestrator is already active before invoking this skill. It operates as a downstream specialization and requires established sandbox assumptions and node ownership. For specific tasks like firmware analysis, malware configuration extraction, or custom protocol replay, use the designated alternative skills referenced in the documentation.

What it helps with

  • reverse engineer a binary file
  • debug crash states and memory dumps
  • recover malware behavior from artifacts
  • verify exploit primitives and chains
  • analyze network PCAP captures

Example prompts for the agent

  • Analyze this binary and identify the crash point.
  • Reverse the memory dump and recover the malware behavior.
  • Verify the exploit chain for this artifact in the sandbox.

How to install competition-reverse-pwn

1Skills CLI (Vercel)

npx skills add zhaoxuya520/reverse-skill --skill competition-reverse-pwn -a claude-code

2Manually: put the files in place

~/.claude/skills/competition-reverse-pwn/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-reverse-pwn/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competition-reverse-pwn

How to install competition-reverse-pwn in Claude Code?

Run the command npx skills add zhaoxuya520/reverse-skill --skill competition-reverse-pwn -a claude-code in your project terminal.

What does competition-reverse-pwn do?

It provides a specialized workflow for binary analysis, forensic triage, and exploit verification within CTF environments.

What is required to run competition-reverse-pwn?

You must have the $ctf-sandbox-orchestrator active, as it establishes the necessary sandbox assumptions, node ownership, and evidence priorities.

Source text

SKILL.md · MIT
---
name: competition-reverse-pwn
description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse engineering, malware, DFIR, firmware, pwnable, and native exploit challenges. Use when the user asks to reverse a binary, unpack a sample, inspect a memory dump or PCAP, recover malware behavior, debug a crash, or build or verify an exploit chain under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition Reverse Pwn

Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.

Use this skill for binary-heavy challenges where the decisive path runs through artifacts, decoded layers, process behavior, crash state, or exploit primitives.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Preserve the original artifact before unpacking, patching, or instrumenting.
2. Start with passive triage: type, headers, sections, imports, strings, entropy, resources.
3. Decide whether the path is reverse-first, DFIR-first, or exploit-first.
4. Tie every claim to an observable boundary: decode edge, persistence edge, crash edge, or leak edge.
5. Reproduce the artifact or primitive from a clean baseline.

## Workflow

### 1. Reverse Or Forensic Triage

- Separate loader, payload, config, and post-decode behavior.
- Correlate files, memory, logs, registry, services, tasks, IPC, and PCAPs as one graph.
- Keep decoded or dumped artifacts separate from the pristine sample.

### 2. Native And Exploit Path

- Map mitigations, loader behavior, libc or runtime, syscall and IPC surfaces, and protocol framing.
- Record the primitive, controllable bytes, leak source, target object, and final artifact separately.
- Compare host, libc, loader, and framing differences before doubting the primitive.

## Read This Reference

- Load `references/reverse-pwn.md` for triage order, exploit evidence expectations, and common failure modes.
- If the task is specifically about staged payload boundaries, config blobs, beacon parameters, or decoded IOC fields, prefer `$competition-malware-config`.
- If the task is specifically about firmware partitions, boot chains, extracted filesystems, or update-package trust boundaries, prefer `$competition-firmware-layout`.
- If the task is specifically about upload parsing, previews, archive extraction, converters, or deserialization chains, prefer `$competition-file-parser-chain`.
- If the task is specifically about source maps, emitted bundles, chunk registries, or reconstructing hidden runtime structure from served frontend assets, prefer `$competition-bundle-sourcemap-recovery`.
- If the task is specifically about container-to-host boundary crossing, kernel exploit preconditions, namespace or cgroup crossover, or escape primitive verification, prefer `$competition-kernel-container-escape`.
- If the task is specifically about reconstructing protocols, streams, or transferred artifacts from packet captures, prefer `$competition-pcap-protocol`.
- If the task is specifically about a custom binary or text protocol where replay state, message order, or checksum logic is the real blocker, prefer `$competition-custom-protocol-replay`.
- If the task is specifically about reconstructing chronology across EVTX, PCAP, registry, mail, or disk artifacts, prefer `$competition-forensic-timeline`.

## What To Preserve

- Offsets, hashes, section names, imports, config blobs, mutexes, registry keys
- Crash offsets, registers, heap or stack shape, leak addresses, and protocol steps
- Original, decoded, dumped, and instrumented artifacts as separate files

© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill

Similar skills

All skills for Security →

From the same set36

The whole set →
competition-identity-windows competition-identity-windows — a skill for Claude Code and Codex that examines Active Directory attacks, Windows host artifacts, and CTF pivot chains. It runs after routing by $ctf-sandbox-orchestrator. CX Codex +1 109installs competition-agent-cloud The competition-agent-cloud Claude Code skill investigates agent and cloud paths in CTF sandboxes. It is routed in after the orchestrator sets the sandbox assumptions, for tracing input-to-tool actions or deployment behavior. CX Codex +1 109installs competition-browser-persistence competition-browser-persistence — a skill for Claude Code that investigates browser persistence surfaces in CTF sandboxes. It activates when stored client state alters request flows, rendering, or access rules. CX Codex +1 109installs competition-ad-certificate-abuse The competition-ad-certificate-abuse Claude Code skill traces certificate-based abuse in AD CS CTF sandboxes. It is triggered by questions about templates, enrollment rights, PKINIT, and privilege paths through certificates. CX Codex +1 109installs competition-supply-chain The competition-supply-chain Claude Code skill traces artifact provenance from source to runtime. It is routed after ctf-sandbox-orchestrator when a challenge involves dependency drift, CI, builds, or releases. CX Codex +1 109installs competition-custom-protocol-replay competition-custom-protocol-replay — a skill for Claude Code decodes custom network protocols and recreates accepted sessions in CTF tasks. Triggers when handling custom framing, checksum rules, and stateful packet sequences. CX Codex +1 109installs competition-runtime-routing The competition-runtime-routing Claude Code skill traces request routing in a CTF sandbox. It maps how hosts, proxy rules, headers, and paths lead to a service or process. CX Codex +1 109installs competition-forensic-timeline competition-forensic-timeline is a Claude Code skill that correlates EVTX, PCAP, registry, and memory artifacts into incident timelines. It runs during DFIR challenges and attack-chain reconstruction. CX Codex +1 109installs

Project sponsors

Companies that keep this analytics open