competition-websocket-runtime — Claude Code skill: what it does
competition-websocket-runtime is a Claude Code skill that inspects WebSocket and SSE handshakes, subscriptions, and frames after the orchestrator runs.
MIT 110 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a claude-codeWhat competition-websocket-runtime does
The skill maps WebSocket and SSE handshakes, authorization parameters, realtime message schemas, and reconnect logic within CTF sandboxes. It operates strictly as a downstream specialization after $ctf-sandbox-orchestrator establishes sandbox assumptions. The workflow covers initial HTTP upgrade requests, message flow decoding, and reduction to the shortest decisive event sequence.
Execution relies on loading references/websocket-runtime.md for checklists and evidence packaging. The agent replies in Simplified Chinese unless English is requested explicitly.
What it helps with
- inspect WebSocket and SSE handshakes
- decode realtime message frames
- trace subscription state and reconnect logic
- verify authorization material during handshake
Example prompts for the agent
- Inspect the WebSocket handshake, headers, and cookies
- Decode the realtime message flow and subscription frames
- Reduce the sequence to the smallest replayable path
How to install competition-websocket-runtime
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a claude-code2Manually: put the files in place
~/.claude/skills/competition-websocket-runtime/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-websocket-runtime/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a codex2Manually: put the files in place
.agents/skills/competition-websocket-runtime/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a cursor2Manually: put the files in place
.cursor/skills/competition-websocket-runtime/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-websocket-runtime/SKILL.md2Manually: put the files in place
.github/skills/competition-websocket-runtime/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-websocket-runtimeManually: put the files in place
.devin/skills/competition-websocket-runtime/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-websocket-runtime
How to install competition-websocket-runtime in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime -a claude-code, then use ~/.claude/skills/competition-websocket-runtime/SKILL.md.
What does competition-websocket-runtime do?
It analyzes WebSocket and SSE handshakes, decodes realtime frames, traces subscription states, and maps session events in downstream sandbox tasks.
What is required to run competition-websocket-runtime?
It requires an active $ctf-sandbox-orchestrator session and the reference file references/websocket-runtime.md.
Source text
SKILL.md · MIT
--- name: competition-websocket-runtime description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for WebSocket and SSE handshakes, auth material, subscription state, realtime message schemas, reconnect behavior, and frame-driven runtime effects. Use when the user asks to inspect a WebSocket or SSE handshake, decode frames, trace subscriptions, follow reconnect logic, inspect auth material sent during realtime setup, or explain how live frames change rendered or persisted state. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition WebSocket Runtime 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 behavior is carried by realtime handshake and frame flow rather than one-shot HTTP alone. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Map the handshake first: origin, path, headers, cookies, query, auth token, and upgrade response. 2. Separate connection setup, subscription messages, keepalives, server pushes, and reconnect logic. 3. Record message schema, topic or channel identity, and state side effects in one chain. 4. Tie frames to rendered, stored, or backend-visible effects. 5. Reproduce the smallest handshake-plus-frame sequence that reaches the decisive state change. ## Workflow ### 1. Map The Realtime Handshake - Record the initial HTTP or SSE request, upgrade headers, cookies, tokens, query params, origin checks, and negotiated protocol. - Note whether auth material is carried by headers, cookies, query strings, or initial application frames. - Keep route, subscription endpoint, and session identity tied together. ### 2. Decode Message Flow - Separate subscribe, unsubscribe, ack, heartbeat, server push, reconnect, and terminal frames. - Recover message types, channel IDs, schema fields, and sequencing that matter to behavior. - Distinguish transport keepalive from application-level business messages. ### 3. Reduce To The Decisive Realtime Path - Compress the result to the smallest sequence: handshake -> auth or subscribe frame -> pushed or accepted frame -> resulting state change. - Keep canonical frame order and any replayed minimal order side by side. - If the hard part is generic protocol reassembly without runtime UI or app-state linkage, switch back to the tighter protocol skill. ## Read This Reference - Load `references/websocket-runtime.md` for the handshake checklist, frame checklist, and evidence packaging. ## What To Preserve - Handshake headers, cookies, query params, auth material, negotiated subprotocol, and channel IDs - Frame schemas, subscription messages, server pushes, reconnect flow, and resulting state changes - The smallest replayable realtime sequence that proves the decisive branch
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill