Competition WebSocket Runtime is a downstream skill of ctf-sandbox-orchestrator for challenges where realtime traffic carries the decisive behavior. It covers handshakes, auth material, subscription state, message schemas and reconnect logic.
The agent separates setup, subscribe, keepalive, push and reconnect frames, then reduces the result to the smallest handshake-plus-frame sequence that reaches the state change. It is written for CTF and lab targets set up by the orchestrator, and replies in Simplified Chinese unless English is requested.
What You Get
- A three-step workflow: map the realtime handshake, decode message flow, reduce to the decisive path
- A handshake checklist covering path, query, cookies, auth headers, Origin, upgrade response and SSE retry directives
- A frame checklist that separates keepalive traffic from business messages
- An evidence layout that keeps setup side, frame side and effect side together
Common Use Cases
- Explaining how a pushed frame changes rendered or stored state in a CTF challenge
- Tracing where a realtime connection carries its auth material
- Reproducing a reconnect or resubscribe behavior that a lab scenario depends on
- Recording the smallest replayable frame sequence for a write-up
What Makes It Unique
It ties frames to effects. Many protocol notes only list messages; this skill requires showing which frame changes state, and it keeps keepalives out of the business logic. It also says when to hand back to a generic protocol skill, namely when no runtime or application state is linked to the capture.
Under The Hood
The skill is a markdown workflow with one reference checklist and an agent metadata file. It ships no scripts. The instructions direct the agent to inspect and replay realtime connections to the sandbox target, so the agent will open network connections and read or send frames through whatever tools the session allows. It applies only after the orchestrator has set sandbox assumptions.