Skip to main content
skill CX Codex

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

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

What 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-code

2Manually: put the files in place

~/.claude/skills/competition-pcap-protocol/SKILL.md

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

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

Similar skills

All skills for Security →
network-forensics-and-pcap-protocol-reconstruction W4L33Dx network-forensics-and-pcap-protocol-reconstruction is a Claude Code skill that rebuilds HTTP, SMB, DNS, and mail sessions from raw packets. Runs during network traffic artifact triage. CX Codex +1 ★ 73repo stars traffic-analysis-pcap yaklang traffic-analysis-pcap is a Claude Code skill that adds a PCAP forensics playbook for analyzing network captures, with Wireshark filters, protocol analysis, DNS tunneling detection, and TLS decryption. CX Codex +1 4,100installs network-forensics-and-pcap W4L33Dx network-forensics-and-pcap is a Claude Code skill that inspects packet captures, rebuilds protocols, and flags suspicious network streams. Processing triggers when pcap files or flow records are provided. CX Codex +1 ★ 73repo stars network-protocol-attacks yaklang A playbook for network protocol attacks: ARP spoofing, LLMNR and NBT-NS poisoning, WPAD abuse, DHCPv6 takeover, VLAN hopping. Built for internal pentests. CX Codex +1 3,900installs competition-zip-archive freyrswift competition-zip-archive is a Claude Code skill that recovers legacy ZipCrypto keys from archives using known-plaintext attacks. CTF workflows trigger it after ctf-sandbox-orchestrator runs. CX Codex +1 ★ 71repo stars Ontario Protocol x402 readiness and Bazaar discovery thom899g Ontario Protocol x402 readiness and Bazaar discovery is an MCP server that checks x402 endpoint readiness, agent payment rules, and paid API discovery in Coinbase Bazaar. CX Codex +1 982installs

From the same set36

The whole set →
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 competition-oauth-oidc-chain competition-oauth-oidc-chain is a Claude Code skill for mapping OAuth/OIDC chains, redirects, and token exchanges after the CTF sandbox orchestrator establishes base assumptions. CX Codex +1 109installs competition-file-parser-chain The competition-file-parser-chain Claude Code skill follows a file from upload to a parser or deserializer. It runs after ctf-sandbox-orchestrator routes a file-processing investigation to it. CX Codex +1 109installs competition-firmware-layout competition-firmware-layout — a skill for Claude Code, Codex, Cursor and other platforms that maps firmware images, partition tables, and boot chains. CX Codex +1 109installs competition-windows-pivot The competition-windows-pivot Claude Code skill traces host-to-host movement in Windows CTF scenarios. It connects recovered credentials or tickets to the service that accepted them. CX Codex +1 109installs

Project sponsors

Companies that keep this analytics open