competition-custom-protocol-replay — Claude Code replay skill
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.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a claude-codeWhat competition-custom-protocol-replay does
The skill reconstructs non-standard binary or text protocols and reproduces the exact message sequence needed to reach an accepted server branch. It inspects client-server roles, maps session transitions from handshake to teardown, tracks field lengths and checksums, and isolates the single mutations that alter server validation.
Execution requires prior routing from $ctf-sandbox-orchestrator once sandbox assumptions are settled. The skill replies in Simplified Chinese unless English is explicitly asked. It relies on references/custom-protocol-replay.md for session mapping checklists and evidence packaging.
What it helps with
- recover proprietary packet framing and message delimiters
- calculate rolling counters and payload checksums
- reproduce minimal message order for accepted sessions
- map handshake and command states across captures
Example prompts for the agent
- Analyze payload framing and checksum logic from this session capture
- Build the minimal message sequence to reach the accepted state
- Reconstruct the custom binary handshake and verify server responses
How to install competition-custom-protocol-replay
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a claude-code2Manually: put the files in place
~/.claude/skills/competition-custom-protocol-replay/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-custom-protocol-replay/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a codex2Manually: put the files in place
.agents/skills/competition-custom-protocol-replay/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a cursor2Manually: put the files in place
.cursor/skills/competition-custom-protocol-replay/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-custom-protocol-replay/SKILL.md2Manually: put the files in place
.github/skills/competition-custom-protocol-replay/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-custom-protocol-replayManually: put the files in place
.devin/skills/competition-custom-protocol-replay/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-custom-protocol-replay
How to install competition-custom-protocol-replay in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay -a claude-code.
What does competition-custom-protocol-replay do?
It analyzes undocumented binary or text protocols, maps state transitions, and creates minimal test harnesses to reach accepted server branches.
What is required before using competition-custom-protocol-replay?
It requires active context from $ctf-sandbox-orchestrator to establish sandbox bounds before running protocol replay.
Source text
SKILL.md · MIT
--- name: competition-custom-protocol-replay description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for custom binary or text protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction. Use when the user asks to decode an unknown protocol, recover custom framing, build a replay harness, satisfy sequence or checksum rules, replay a captured session, or prove the smallest message order that reaches an accepted branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Custom Protocol Replay 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 when the hard part is not merely naming the protocol, but reproducing the exact message order and state needed for acceptance. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Identify client and server roles, session boundaries, and reset conditions before decoding field semantics. 2. Recover framing, lengths, delimiters, sequence numbers, checksums, nonces, and state transitions before broad replay attempts. 3. Keep one canonical transcript of a successful exchange. 4. Change one field or one message at a time while replaying. 5. Reproduce the smallest accepted conversation that proves the decisive branch. ## Workflow ### 1. Map The Session State Machine - Identify handshake, negotiation, authentication, keepalive, command, and teardown phases. - Record which fields are static, which are derived, and which depend on prior messages. - Keep message order, direction, and timing tied to the same session identity. ### 2. Recover Framing And Integrity - Reconstruct lengths, delimiters, type bytes, checksums, MACs, counters, compression, or encryption boundaries. - Distinguish transport framing from application-level framing. - Note exactly where server acceptance changes when one field or step is mutated. ### 3. Build The Minimal Replay Harness - Reduce the path to the smallest transcript that reaches the accepted state, parser branch, command effect, or artifact. - Preserve both the original captured sequence and the replayed minimal sequence. - If the problem is mainly generic PCAP or stream decoding with no stateful replay requirement, switch back to the broader PCAP skill. ## Read This Reference - Load `references/custom-protocol-replay.md` for the state-machine checklist, transcript checklist, and evidence packaging. ## What To Preserve - Canonical transcript, message types, field boundaries, checksums, counters, and session identifiers - Original capture slices and the replay harness inputs that produce acceptance - The exact mutation that flips the protocol from rejected to accepted, or vice versa
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill