Skip to content
SkillModel-led568 tokens in use

competition-pcap-protocol

A CTF sandbox workflow for rebuilding sessions from packet captures and tying decoded streams to host or malware behavior.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-pcap-protocol
git clone https://github.com/zhaoxuya520/reverse-skill.git
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing competition-pcap-protocol costs

118tokens idle
568tokens in use
804tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples0/15
  • Output10/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a downstream specialization of the ctf-sandbox-orchestrator skill. It guides an agent through packet capture analysis in a CTF sandbox: capture boundaries, session grouping, stream reassembly, protocol framing and the link between packets and host behavior.

It fits challenges where the decisive evidence sits in packet order or framing, such as HTTP, WebSocket, DNS or custom command channels. It points to sibling skills for WebSocket runtime work, custom protocol replay and forensic timelines. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A session-first method that avoids reasoning from single packets
  • A decode order covering reassembly, framing, compression, encoding and object extraction
  • A checklist of what to preserve: stream IDs, endpoint pairs, packet ranges and timestamps
  • Hand-off pointers to the WebSocket, custom protocol and forensic timeline skills

Common Use Cases

  • Rebuilding TCP or UDP conversations from a capture in a CTF challenge
  • Decoding a custom command or beacon channel and extracting transferred files
  • Linking a packet sequence to a login, upload or exfiltration step in a lab

What Makes It Unique

It centres on stream reconstruction and decoded content, and it separates control channels, bulk transfers and noise before decoding. Related problems are routed to narrower sibling skills, and it runs only after the orchestrator skill has set sandbox assumptions.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent config file that disables implicit invocation. It ships no scripts and does not itself fetch pages, call APIs, run commands or write files. The agent applies the method with whatever packet tools the user already has in the sandbox.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers