CtrlK
BlogDocsLog inGet started
Tessl Logo

hunt-websocket

Hunt WebSocket vulnerabilities — Cross-Site WebSocket Hijacking (CSWSH), missing/weak Origin validation on the WS handshake, no per-message authentication, message tampering, socket.io namespace/room authorization bypass, and handshake-layer Upgrade smuggling. Use when target has WebSocket endpoints (ws:// or wss://), socket.io / SignalR / Phoenix Channels, real-time features, chat, live dashboards, notifications, or trading platforms.

74

Quality

92%

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

85%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 highly actionable, well-sequenced hunting playbook with strong validation discipline and copy-paste tooling. Its main weakness is progressive disclosure: all detail lives inline in SKILL.md with no reference files to offload the reference-cases table and packet-level specifics.

Suggestions

Move the Grounding reference-cases table and CVE details into a references/ file (e.g. REFERENCES.md) and link to it from a short 'Grounding' stub, reducing SKILL.md length and giving the CVEs a stable, updatable home.

Extract the packet-level socket.io/Engine.IO specifics (Phase 5 and Phase 7) into a references/socketio.md file, keeping SKILL.md as the overview that points one level deep.

Trim redundancy between the Crown Jewel Targets, Chain Table, and final Severity sections — consolidate impact/severity into the Chain Table and drop the duplicated prose.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no basic 'what is a WebSocket' padding), but the Crown Jewel Targets, Chain Table, and final Validation/Severity sections restate overlapping chain/impact information that could be trimmed, sitting just below the 'every token earns its place' anchor.

4 / 5

Actionability

Copy-paste-ready bash (wscat, curl, nmap, grep), a complete attacker-origin HTML PoC, and exact socket.io packet bytes (40/admin,) make the guidance fully executable across the common cases.

5 / 5

Workflow Clarity

Seven sequenced phases each carry inline 'Validate:' checkpoints, a dedicated mandatory Validation checklist, and False-Positive Killers feedback loops, satisfying the explicit-validation + error-recovery anchor with no missing validation cap.

5 / 5

Progressive Disclosure

Internally well-sectioned, but the ~280-line body is monolithic with no bundle files or one-level-deep references; the Grounding reference-cases table and packet-level socket.io specifics are inlined rather than split into reference files, matching the 'some structure but content that should be separate is inline' anchor.

3 / 5

Total

17

/

20

Passed

Description

100%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.

The description is excellent: third-person imperative voice, dense with concrete vulnerability classes, and paired with an explicit, trigger-rich 'Use when' clause. It distinguishes itself clearly from sibling hunting skills.

DimensionReasoningScore

Specificity

Names six concrete vulnerability classes (CSWSH, missing/weak Origin validation, no per-message authentication, message tampering, socket.io namespace/room authorization bypass, handshake-layer Upgrade smuggling), matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

Explicitly answers 'what' (hunt these WS vulnerabilities) and 'when' via a concrete 'Use when target has WebSocket endpoints...' clause, matching the anchor for clearly answering both what AND when.

5 / 5

Trigger Term Quality

Covers natural terms users would say including protocol schemes (ws://, wss://), frameworks (socket.io, SignalR, Phoenix Channels), and feature triggers (chat, live dashboards, notifications, trading platforms), matching comprehensive synonym/extension coverage.

5 / 5

Distinctiveness Conflict Risk

A clearly scoped WebSocket-only hunting niche with protocol/framework-specific triggers that minimize overlap with other hunt skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
elementalsouls/Claude-BugHunter
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.