Name: competition-custom-protocol-replay
Author: zhaoxuya520

Imported from zhaoxuya520/reverse-skill (CTF-Sandbox-Orchestrator/competition-custom-protocol-replay/SKILL.md). Install upstream with npx skills add zhaoxuya520/reverse-skill --skill competition-custom-protocol-replay. Copyright stays with the author.

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

Identify client and server roles, session boundaries, and reset conditions before decoding field semantics.
Recover framing, lengths, delimiters, sequence numbers, checksums, nonces, and state transitions before broad replay attempts.
Keep one canonical transcript of a successful exchange.
Change one field or one message at a time while replaying.
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

Install competition-custom-protocol-replay and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zhaoxuya520-reverse-skill-competition-custom-protocol-replay", "kind": "skill", "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.", "publisher": "zhaoxuya520", "version": "1.0.0", "capabilities": { "domains": [ "math" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zhaoxuya520/reverse-skill", "path": "CTF-Sandbox-Orchestrator/competition-custom-protocol-replay/SKILL.md", "ref": "HEAD", "url": "https://github.com/zhaoxuya520/reverse-skill/blob/HEAD/CTF-Sandbox-Orchestrator/competition-custom-protocol-replay/SKILL.md", "key": "zhaoxuya520/reverse-skill/CTF-Sandbox-Orchestrator/competition-custom-protocol-replay/SKILL.md" } }, "instructions": "# Competition Custom Protocol Replay\n\nUse 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.\n\nUse this skill when the hard part is not merely naming the protocol, but reproducing the exact message order and state needed for acceptance.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Identify client and server roles, session boundaries, and reset c", "cost": { "context_tokens": 601 } }

competition-custom-protocol-replay

About