competition-pcap-protocol

Reconstruct PCAP sessions, decode application protocols, and correlate packets with host behavior.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/MDSIXONE/opencode-config --skill competition-pcap-protocol-mdsixone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competition-pcap-protocol
Source: https://github.com/MDSIXONE/opencode-config/tree/main/skills/reverse-skill/CTF-Sandbox-Orchestrator/competition-pcap-protocol
Command: npx skills add https://github.com/MDSIXONE/opencode-config --skill competition-pcap-protocol-mdsixone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Analyzing packet captures in CTF and sandbox scenarios often stalls when evidence is scattered across individual packets, fragmented streams, or undecoded custom protocols. This Skill provides a structured workflow for rebuilding sessions, decoding protocol framing, and tying packet sequences to concrete host or malware behavior. ## Core Features & Use Cases - Session Reconstruction: Group traffic into TCP/UDP sessions, identify endpoints, TLS handshakes, DNS lookups, WebSocket upgrades, and long-lived streams before decoding payloads. - Protocol Decoding: Reassemble streams to recover framing, message order, custom headers, binary fields, compression, and transferred artifacts for HTTP, DNS, WebSocket, custom C2, or binary protocols. - Behavior Correlation: Map decoded packet sequences to host events, malware branches, login flows, uploads, exfiltration steps, or command channels. - Use Case: During a CTF challenge, you receive a PCAP containing a covert C2 channel. Use this Skill to rebuild the session, decode the custom framing, extract the transferred payload, and prove which packet sequence triggered the malware's exfiltration branch. ## Quick Start After $ctf-sandbox-orchestrator is active, use $competition-pcap-protocol to reconstruct the sessions in this PCAP, decode the application protocol, and tie the packet evidence to the challenge behavior.

Frequently Asked Questions about competition-pcap-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a PCAP file in a CTF challenge?▼

Start by establishing capture boundaries: hosts, time span, interfaces, missing packets, and stream count. Then group traffic into sessions, reassemble TCP streams or UDP conversations, and decode protocol framing before interpreting payload semantics.

How to decode custom C2 or binary protocols from packet captures?▼

Reassemble the full stream first, then recover framing markers, message order, custom headers, binary fields, and any compression or encryption boundaries. Keep payload direction, timing, and session state aligned with each decoded message.

When should I use this skill instead of a WebSocket or custom protocol skill?▼

Use this skill for general session reconstruction and protocol decoding. If the hard part is WebSocket or SSE handshake and frame-driven state, use the websocket runtime skill; for custom handshakes, checksums, or replay harnesses, use the custom protocol replay skill.

Why does single-packet analysis fail in PCAP investigations?▼

Single packets lack the stream context needed to interpret fields correctly. Reasoning from isolated packets misses reassembly requirements, message ordering, and session state, leading to wrong conclusions about protocol behavior.

What evidence should be preserved from a PCAP analysis?▼

Preserve stream IDs, endpoint pairs, packet ranges, timestamps, protocol framing, and object boundaries. Keep decoded requests, responses, commands, and transferred files together with the session that carried them and the behavioral link they prove.