competition-websocket-runtime

Name: competition-websocket-runtime
Author: zhaoxuya520

8.8kstars1.4kforks

How to install competition-websocket-runtime?

zhaoxuya520/reverse-skill/competition-websocket-runtime

$npx -y skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime

Installs into the current project.

Summary

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 h

Files · 1

View on GitHub

SKILL.md

1	# Competition WebSocket Runtime
2
3	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.
4
5	Use this skill when the decisive behavior is carried by realtime handshake and frame flow rather than one-shot HTTP alone.
6
7	Reply in Simplified Chinese unless the user explicitly requests English.
8
9	## Quick Start
10
11	1. Map the handshake first: origin, path, headers, cookies, query, auth token, and upgrade response.
12	2. Separate connection setup, subscription messages, keepalives, server pushes, and reconnect logic.
13	3. Record message schema, topic or channel identity, and state side effects in one chain.
14	4. Tie frames to rendered, stored, or backend-visible effects.
15	5. Reproduce the smallest handshake-plus-frame sequence that reaches the decisive state change.
16
17	## Workflow
18
19	### 1. Map The Realtime Handshake
20
21	- Record the initial HTTP or SSE request, upgrade headers, cookies, tokens, query params, origin checks, and negotiated protocol.
22	- Note whether auth material is carried by headers, cookies, query strings, or initial application frames.
23	- Keep route, subscription endpoint, and session identity tied together.
24
25	### 2. Decode Message Flow
26
27	- Separate subscribe, unsubscribe, ack, heartbeat, server push, reconnect, and terminal frames.
28	- Recover message types, channel IDs, schema fields, and sequencing that matter to behavior.
29	- Distinguish transport keepalive from application-level business messages.
30
31	### 3. Reduce To The Decisive Realtime Path
32
33	- Compress the result to the smallest sequence: handshake -> auth or subscribe frame -> pushed or accepted frame -> resulting state change.
34	- Keep canonical frame order and any replayed minimal order side by side.
35	- If the hard part is generic protocol reassembly without runtime UI or app-state linkage, switch back to the tighter protocol skill.
36
37	## Read This Reference
38
39	- Load `references/websocket-runtime.md` for the handshake checklist, frame checklist, and evidence packaging.
40
41	## What To Preserve
42
43	- Handshake headers, cookies, query params, auth material, negotiated subprotocol, and channel IDs
44	- Frame schemas, subscription messages, server pushes, reconnect flow, and resulting state changes
45	- The smallest replayable realtime sequence that proves the decisive branch

People who liked this also viewed

6 picks

Type

competition-websocket-runtime

8.8kstars1.4kforks

View on GitHub

How to install competition-websocket-runtime?

zhaoxuya520/reverse-skill/competition-websocket-runtime

$npx -y skills add zhaoxuya520/reverse-skill --skill competition-websocket-runtime

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Competition WebSocket Runtime
2
3	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.
4
5	Use this skill when the decisive behavior is carried by realtime handshake and frame flow rather than one-shot HTTP alone.
6
7	Reply in Simplified Chinese unless the user explicitly requests English.
8
9	## Quick Start
10
11	1. Map the handshake first: origin, path, headers, cookies, query, auth token, and upgrade response.
12	2. Separate connection setup, subscription messages, keepalives, server pushes, and reconnect logic.
13	3. Record message schema, topic or channel identity, and state side effects in one chain.
14	4. Tie frames to rendered, stored, or backend-visible effects.
15	5. Reproduce the smallest handshake-plus-frame sequence that reaches the decisive state change.
16
17	## Workflow
18
19	### 1. Map The Realtime Handshake
20
21	- Record the initial HTTP or SSE request, upgrade headers, cookies, tokens, query params, origin checks, and negotiated protocol.
22	- Note whether auth material is carried by headers, cookies, query strings, or initial application frames.
23	- Keep route, subscription endpoint, and session identity tied together.
24
25	### 2. Decode Message Flow
26
27	- Separate subscribe, unsubscribe, ack, heartbeat, server push, reconnect, and terminal frames.
28	- Recover message types, channel IDs, schema fields, and sequencing that matter to behavior.
29	- Distinguish transport keepalive from application-level business messages.
30
31	### 3. Reduce To The Decisive Realtime Path
32
33	- Compress the result to the smallest sequence: handshake -> auth or subscribe frame -> pushed or accepted frame -> resulting state change.
34	- Keep canonical frame order and any replayed minimal order side by side.
35	- If the hard part is generic protocol reassembly without runtime UI or app-state linkage, switch back to the tighter protocol skill.
36
37	## Read This Reference
38
39	- Load `references/websocket-runtime.md` for the handshake checklist, frame checklist, and evidence packaging.
40
41	## What To Preserve
42
43	- Handshake headers, cookies, query params, auth material, negotiated subprotocol, and channel IDs
44	- Frame schemas, subscription messages, server pushes, reconnect flow, and resulting state changes
45	- The smallest replayable realtime sequence that proves the decisive branch

People who liked this also viewed

6 picks

Type