CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-websocket

WebSocket exploitation — origin-bypass (CSWSH cross-site WebSocket hijacking), missing per-message auth, message-type confusion, msg-flood DoS, ws→wss downgrade, hidden RPC routes in the WS frame layer.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 dense, high-signal body that delivers executable commands and PoCs for the main WebSocket bug classes with minimal token waste. The main gaps are executable test recipes for the downgrade and DoS classes, and the option to split protocol-specific material into a reference file.

DimensionReasoningScore

Conciseness

The ~105-line body is lean and every section earns its place: a copy-paste curl handshake probe, minimal PoCs, terse protocol tips ("`SUBSCRIBE /topic/admin` often missing authz"), and OPSEC notes that carry non-obvious knowledge ("WAFs often DON'T inspect WS frames"). It assumes Claude's competence with no padding or explanation of basics, matching the level-5 anchor.

5 / 5

Actionability

Mostly executable guidance — the curl handshake test, the CSWSH HTML PoC, wscat command lines, and a runnable Python snippet are copy-paste ready, with result-interpretation cues ("101 = upgraded", "If server accepts → CSWSH"). It falls short of anchor 5 because the ws→wss downgrade section ("MITM to drop the upgrade") and the msg-flood DoS class from the description have no executable commands, and the Python snippet omits installing the websocket-client dependency.

4 / 5

Workflow Clarity

A clear Detect-then-test sequence (Detect → Top 5 bug classes → Tooling → Protocol-specific tips → OPSEC) with interpretation cues acting as implicit checkpoints ("Distinct error per route reveals what exists vs what's gated"). It is not 5 because validation is implicit rather than explicit — there is no stated verify/interpret step per bug class — though this is a testing methodology, not a destructive batch operation, so the level-3 cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is cleanly sectioned and easy to navigate, with appropriate inline placement for most content. It sits at anchor 4 rather than 5 because the protocol-specific tips (Socket.IO, STOMP, GraphQL-WS, SignalR) and the tooling section are natural candidates for a one-level-deep reference file, keeping the body at ~105 lines instead of a tighter overview.

4 / 5

Total

17

/

20

Passed

Description

75%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 highly specific, well-differentiated description that names concrete WebSocket attack classes without vague padding. Its one structural weakness is that all 'when to use' trigger guidance is delegated to the metadata.when_to_use field instead of appearing in the description itself, capping completeness at 3.

Suggestions

Append an explicit 'Use when...' clause to the description itself, e.g. "Use when testing WebSocket endpoints over ws/wss, including socket.io, STOMP, GraphQL-WS, ActionCable, or SignalR" — this moves the trigger guidance from metadata into the description and lifts completeness.

Add one or two natural trigger phrases users actually say (e.g. "websocket security testing", "real-time messaging security") to improve trigger_term_quality beyond the current synonym set of ws/wss/CSWSH.

DimensionReasoningScore

Specificity

The description enumerates six concrete attack techniques ("origin-bypass (CSWSH cross-site WebSocket hijacking)", "missing per-message auth", "message-type confusion", "msg-flood DoS", "ws→wss downgrade", "hidden RPC routes") — comprehensive coverage of the WebSocket attack surface with no vague filler, matching the level-5 anchor rather than the level-4 anchor's 'minor gaps'.

5 / 5

Completeness

The description clearly answers 'what' (the enumerated exploitation classes) but contains no 'Use when...' clause or equivalent explicit trigger guidance — that guidance lives in the separate metadata.when_to_use field, not the description itself. Per the judging guideline, a missing 'when' clause caps completeness at 3; it is not 4 because the 'when' is genuinely absent rather than merely imprecise, and not 2 because the 'what' is specific and comprehensive.

3 / 5

Trigger Term Quality

Strong keyword coverage with synonym variants ("WebSocket", "ws→wss", "WS frame layer", and CSWSH both as acronym and expanded), but natural phrases a user might say such as "websocket security testing", "socket.io", "STOMP", or "real-time messaging" are absent — good coverage with a few terms missing, matching anchor 4 rather than anchor 5's comprehensive synonym set.

4 / 5

Distinctiveness Conflict Risk

"WebSocket exploitation" plus attack-specific terms (CSWSH, msg-flood DoS, per-message auth) define a clear niche with distinct triggers that would not fire for non-WebSocket skills — minimal conflict risk, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/exploit/api/websocket/SKILL.md

Reviewed

Table of Contents

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.