How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

competition-pcap-protocol - Skill

Name: competition-pcap-protocol
Author: zhaoxuya520

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

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

Establish the capture boundaries first: hosts, time span, interfaces, missing packets, retransmits, and stream count.
Group traffic into sessions before decoding payload semantics.
Record protocol framing, sequence, timing, and transferred artifacts together instead of as isolated packets.
Correlate packet evidence with host, malware, or app behavior only after the session is reconstructed.
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

Install competition-pcap-protocol 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-pcap-protocol", "kind": "skill", "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.", "publisher": "zhaoxuya520", "version": "1.0.0", "capabilities": { "domains": [ "data_analysis", "observability" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zhaoxuya520/reverse-skill", "path": "CTF-Sandbox-Orchestrator/competition-pcap-protocol/SKILL.md", "ref": "HEAD", "url": "https://github.com/zhaoxuya520/reverse-skill/blob/HEAD/CTF-Sandbox-Orchestrator/competition-pcap-protocol/SKILL.md", "key": "zhaoxuya520/reverse-skill/CTF-Sandbox-Orchestrator/competition-pcap-protocol/SKILL.md" } }, "instructions": "# Competition PCAP Protocol\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 decisive evidence sits inside packet order, protocol framing, or stream reconstruction rather than a single IOC or host log.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Establish the capture boundaries first: hosts, time span, interfaces, missing packets, retransmits, and stream count.\n2. Group traffic into sessions before decoding payload semantics.\n3. Record protocol framing, sequence, timing, and transferred artifacts together instead of as isolated packets.\n4. Correlate packet evidence with host, malware, or app behavior only after the session is reconstructed.\n5. Reproduce the smallest decoded stream or transferred artifact that proves the challenge path.\n\n## Workflow\n\n### 1. Build The Session Map\n\n- Identify endpoints, protocols, ports, TLS handshakes, DNS lookups, websocket upgrades, and long-lived streams.\n- Note missing capture coverage, asymmetric routing, packet loss, or reassembly issues before drawing conclusions.\n- Separate control channels, bulk transfers, keepalives, and noise.\n\n### 2. Decode The Protocol Boundary\n\n- Reassemble TCP streams or UDP conversations before interpreting fields.\n- Recover framing, message order, custom headers, binary fields, compression, encryption boundaries, and object transfers.\n- Keep payload direction, timing, and session state aligned with each decoded message.\n\n### 3. Tie Packets To Behavior\n\n- Show which packet sequence maps to which host event, malware branch, login flow, upload, exfiltration step, or command channel.\n- Distinguish protocol recognition from artifact recovery: naming HTTP, DNS, or a custom C2 is not enough without decoded content or proven downstream effect.\n- If the task becomes mostly a host timeline problem after decode, switch to the tighter forensic timeline skill.\n\n## Read This Reference\n\n- Load `references/pcap-protocol.md` for the session checklist, decode checklist, and evidence packaging.\n- If the hard part is a WebSocket or SSE handshake, subscription flow, realtime frames, or frame-driven state, prefer `$competition-websocket-runtime`.\n- If the hard part is a custom handshake, framing, checksum, sequence dependency, or deterministic replay harness, prefer `$competition-custom-protocol-replay`.\n\n## What To Preserve\n\n- Stream IDs, endpoint pairs, packet ranges, timestamps, protocol framing, and object boundaries\n- Decoded requests, responses, commands, transferred files, and the session that carried them\n- The exact packet sequence or reconstructed stream that proves the challenge behavior", "cost": { "context_tokens": 718 } }

competition-pcap-protocol

About

Competition PCAP Protocol

Quick Start

Workflow

1. Build The Session Map

2. Decode The Protocol Boundary

3. Tie Packets To Behavior

Read This Reference

What To Preserve

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

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews