competition-websocket-runtime

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured analysis skill with a clean one-level reference split and concrete capture checklists. The main weaknesses are Quick-Start/Workflow redundancy and the absence of an explicit reproduction-failure feedback loop or worked example.

Suggestions

Collapse the redundancy between Quick Start and Workflow — steps 1–3 of Quick Start restate Workflow sections 1–3; keep one as overview and one as detail to recover tokens.

Add a short worked example of a minimal handshake → auth/subscribe → pushed frame → state-change sequence (inline or in the reference) so the analysis guidance covers a common concrete case.

Add an explicit feedback loop after the reproduction step: if the replayed sequence does not reach the decisive state change, re-examine auth carriers and subscription frames before concluding.

Dimension	Reasoning	Score
Conciseness	Language is lean and assumes Claude's competence (no explaining what a WebSocket is), but the Quick Start steps 1–3 restate the three Workflow sections on handshake mapping, message-flow decoding, and the decisive path, so not every token earns its place.	4 / 5
Actionability	Concrete, specific checklists ('origin, path, headers, cookies, query, auth token, and upgrade response'; 'subscribe, unsubscribe, ack, heartbeat, server push, reconnect, and terminal frames') tell Claude exactly what to capture, but no worked example of a decoded handshake-plus-frame sequence is provided.	4 / 5
Workflow Clarity	A clear five-step Quick Start and a three-section Workflow give an unambiguous sequence (map handshake → decode flow → reduce to decisive path) ending in a reproduction checkpoint, but there is no explicit error-recovery feedback loop if reproduction fails.	4 / 5
Progressive Disclosure	The body is a tight overview with one clearly signaled, one-level-deep reference — 'Load `references/websocket-runtime.md` for the handshake checklist, frame checklist, and evidence packaging' — and that file exists and holds the detailed checklists, keeping navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that concretely states capabilities, gives explicit natural trigger phrases, and hard-gates itself behind the orchestrator skill to avoid conflicts. The only gap is synonym breadth in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the realtime domain — 'inspect a WebSocket or SSE handshake, decode frames, trace subscriptions, follow reconnect logic, inspect auth material... explain how live frames change rendered or persisted state' — giving comprehensive coverage rather than a single generic action.	5 / 5
Completeness	Explicitly states both what ('workflow for WebSocket and SSE handshakes, auth material, subscription state, realtime message schemas, reconnect behavior, and frame-driven runtime effects') and when ('Use when the user asks to inspect... decode frames, trace subscriptions...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases a debugging user would say are present ('inspect a WebSocket handshake', 'decode frames', 'trace subscriptions', 'follow reconnect logic'), but synonym coverage is thin — no 'push messages', 'streaming', 'live updates', 'events', or 'Server-Sent Events' variants.	4 / 5
Distinctiveness Conflict Risk	Clear niche (CTF-sandbox realtime runtime) with explicit routing boundary — 'Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here' — minimizing overlap with sibling skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zhaoxuya520/reverse-skill
Path: CTF-Sandbox-Orchestrator/competition-websocket-runtime/SKILL.md
Commit: 7e2097f

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.