competition-pcap-protocol — Claude Code skill for PCAP analysis
The competition-pcap-protocol Claude Code skill reconstructs sessions and decodes traffic in packet captures. It runs after sandbox setup when packet evidence needs to be tied to host or malware activity.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -a claude-codeWhat competition-pcap-protocol does
The skill groups captured traffic into sessions, reconstructs TCP streams and UDP conversations, and decodes protocol framing. It can recover transferred files and connect packet sequences to host events, malware behavior, or command traffic.
ctf-sandbox-orchestrator must establish the sandbox assumptions and evidence priorities first, then route the task here. The analysis tracks timestamps, traffic direction, packet loss, and object boundaries. For session and decoding checklists, plus evidence packaging guidance, the skill loads references/pcap-protocol.md.
If the task turns into a host event timeline, it switches to a focused forensic timeline skill. Separate skills cover difficult WebSocket flows and replaying custom protocols.
What it helps with
- rebuild a TCP or UDP session from a PCAP
- decode HTTP, DNS, or custom protocol traffic
- recover files transferred over a network stream
- connect packet sequences to host or malware behavior
Example prompts for the agent
- Analyze this PCAP and reconstruct its TCP and UDP sessions.
- Decode the DNS and HTTP traffic, then recover transferred files.
- Link this packet sequence to the malware's behavior.
How to install competition-pcap-protocol
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -a claude-code2Manually: put the files in place
~/.claude/skills/competition-pcap-protocol/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-pcap-protocol/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -a codex2Manually: put the files in place
.agents/skills/competition-pcap-protocol/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -a cursor2Manually: put the files in place
.cursor/skills/competition-pcap-protocol/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-pcap-protocol/SKILL.md2Manually: put the files in place
.github/skills/competition-pcap-protocol/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-pcap-protocolManually: put the files in place
.devin/skills/competition-pcap-protocol/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -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-pcap-protocol
How do I install competition-pcap-protocol in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-pcap-protocol -a claude-code. The skill file is at ~/.claude/skills/competition-pcap-protocol/SKILL.md.
What does competition-pcap-protocol do?
It reconstructs sessions and decodes protocols in PCAP captures, recovers transferred files, and relates packet evidence to host or malware activity.
What does competition-pcap-protocol need to run?
ctf-sandbox-orchestrator must establish the sandbox assumptions and route the task to this skill first.
Source text
SKILL.md · MIT
--- name: competition-pcap-protocol description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for packet capture analysis, session reconstruction, application-protocol decoding, stream reassembly, beacon timing, and packet-to-process correlation. Use when the user asks to analyze a PCAP, rebuild TCP or UDP sessions, decode HTTP, WebSocket, DNS, custom C2, or binary protocols, extract transferred artifacts, or tie packet sequences to host or malware behavior. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition PCAP Protocol 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 decisive evidence sits inside packet order, protocol framing, or stream reconstruction rather than a single IOC or host log. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Establish the capture boundaries first: hosts, time span, interfaces, missing packets, retransmits, and stream count. 2. Group traffic into sessions before decoding payload semantics. 3. Record protocol framing, sequence, timing, and transferred artifacts together instead of as isolated packets. 4. Correlate packet evidence with host, malware, or app behavior only after the session is reconstructed. 5. Reproduce the smallest decoded stream or transferred artifact that proves the challenge path. ## Workflow ### 1. Build The Session Map - Identify endpoints, protocols, ports, TLS handshakes, DNS lookups, websocket upgrades, and long-lived streams. - Note missing capture coverage, asymmetric routing, packet loss, or reassembly issues before drawing conclusions. - Separate control channels, bulk transfers, keepalives, and noise. ### 2. Decode The Protocol Boundary - Reassemble TCP streams or UDP conversations before interpreting fields. - Recover framing, message order, custom headers, binary fields, compression, encryption boundaries, and object transfers. - Keep payload direction, timing, and session state aligned with each decoded message. ### 3. Tie Packets To Behavior - Show which packet sequence maps to which host event, malware branch, login flow, upload, exfiltration step, or command channel. - Distinguish protocol recognition from artifact recovery: naming HTTP, DNS, or a custom C2 is not enough without decoded content or proven downstream effect. - If the task becomes mostly a host timeline problem after decode, switch to the tighter forensic timeline skill. ## Read This Reference - Load `references/pcap-protocol.md` for the session checklist, decode checklist, and evidence packaging. - If the hard part is a WebSocket or SSE handshake, subscription flow, realtime frames, or frame-driven state, prefer `$competition-websocket-runtime`. - If the hard part is a custom handshake, framing, checksum, sequence dependency, or deterministic replay harness, prefer `$competition-custom-protocol-replay`. ## What To Preserve - Stream IDs, endpoint pairs, packet ranges, timestamps, protocol framing, and object boundaries - Decoded requests, responses, commands, transferred files, and the session that carried them - The exact packet sequence or reconstructed stream that proves the challenge behavior
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill