CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-server-sent-events

Server-Sent Events (SSE / EventSource) exploitation — origin abuse for cross-site streaming exfil, prompt-injection via SSE messages into LLM clients, retry-after token leak, fragmenting events to bypass content-type sniffers.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/exploit/api/server-sent-events/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 well-organized single-file catalog of SSE attack classes with genuinely executable detection code and a strong cross-origin exfil PoC, plus practical OPSEC notes. Roughly half the bug classes remain descriptive rather than testable, the intro re-explains SSE basics, and no explicit workflow with verification checkpoints ties the sections together.

Suggestions

Add runnable PoCs or test commands for the currently describe-only classes — e.g. a socket-level or Python snippet for the reconnect/Last-Event-ID token leak and a bounded concurrency script for the retry-behavior check instead of 'Burst 10k clients → exhaustion'.

Delete the opening explainer of what SSE is and where it's used; Claude already knows this, and it costs tokens without adding attack-specific value.

Make the workflow explicit — a short ordered sequence (1. confirm text/event-stream, 2. test each class, 3. verify impact before reporting) with verification checkpoints for confirming each finding.

DimensionReasoningScore

Conciseness

The body is mostly tight and code-driven, but it opens by explaining what SSE is and where it's used ("SSE is one-way (server → browser) over HTTP/1.1 or HTTP/2...", "Used by LLM chat UIs, live dashboards...") — concepts Claude already knows — and bug class 5 is speculative filler ("may be mis-classified... Niche but appears in legacy integrations"). It fits 'mostly efficient with some unnecessary explanation' better than 'efficient with only minor trimming'.

3 / 5

Actionability

Detect (curl), bug class 1 (copy-paste HTML/JS PoC), and Tooling (curl/python sseclient/Burp notes) are executable, but bug classes 3, 4, and 5 are describe-only — "Burst 10k clients → exhaustion" and the Last-Event-ID leak give direction without any runnable test or PoC. That's more than minor gaps, so it sits below the 'mostly executable' anchor.

3 / 5

Workflow Clarity

The order is implicitly sensible (Detect first, then enumerated bug classes, then Tooling/OPSEC), but there is no explicit sequence connecting the sections and no verification checkpoints for confirming a finding (e.g. how to verify the CORS misconfig actually reflects credentials or that the exfil fires). The body exceeds the under-50-line simple-skill exception, so implicit ordering and missing checkpoints hold it at 3.

3 / 5

Progressive Disclosure

No bundle files exist, and the single-file structure is clean — Detect, five numbered bug classes, Tooling, OPSEC, and a clearly signaled References section with external links one level deep. It misses 5 only because the body (~95 lines) exceeds the under-50-line simple-skill threshold and the reference links are bare names rather than well-signaled navigation to skill content.

4 / 5

Total

13

/

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, distinctive description that names four concrete SSE attack classes with good keyword coverage. Its main weakness is the absence of any explicit "Use when..." trigger clause, which caps completeness and leaves activation guidance buried in metadata.when_to_use.

Suggestions

Append an explicit 'Use when...' clause to the description, e.g. "Use when testing SSE endpoints, EventSource integrations, streaming responses, or text/event-stream APIs."

Move natural trigger terms currently only in metadata.when_to_use (e.g. "text/event-stream", "reconnect", "streaming endpoint") into the description itself so trigger coverage is comprehensive.

State the skill's output or purpose framing (e.g. 'detect and exploit') so the 'what' reads as capability statements rather than a bare topic list.

DimensionReasoningScore

Specificity

The description lists multiple concrete attack classes — "origin abuse for cross-site streaming exfil, prompt-injection via SSE messages into LLM clients, retry-after token leak, fragmenting events to bypass content-type sniffers" — giving comprehensive, specific coverage of the domain rather than generic claims.

5 / 5

Completeness

The "what" is clear and concrete (four named SSE exploitation classes), but the description contains no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines; trigger timing is only weakly implied by the domain keywords.

3 / 5

Trigger Term Quality

"Server-Sent Events (SSE / EventSource)" covers the key synonyms a user would naturally say, and terms like "retry" and "prompt-injection" are natural to this niche. However, common variations such as "text/event-stream", "streaming endpoint", or "reconnect" appear only in metadata.when_to_use, not in the description itself, so coverage is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

SSE/EventSource exploitation is a clear, narrow niche with distinct technical triggers ("SSE / EventSource", "text/event-stream" semantics, "retry-after"), making conflict with other skills minimal.

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/server-sent-events/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.