Content
82%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |