CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/server-sent-events-tests

Test Server-Sent Events (SSE) flows, one-way server-to-client push only (not bidirectional, use websocket-tests for client-to-server messaging): `EventSource` API on the browser side (`onmessage`, `onerror`, `readyState` 0/1/2), event stream format (`data:`, `event:`, `id:`, `retry:`), `Last-Event-ID` reconnect-with-replay header, content-type `text/event-stream`, and HTTP/1.1 connection-pool limits. Use Playwright for browser-side, raw HTTP client for server-side stream tests; k6 load testing (concurrent-stream capacity, connection churn, HTTP/1.1 vs HTTP/2 ceiling) lives in references/sse-load.md. Use when a feature pushes updates over `text/event-stream` and the reconnect interval, `Last-Event-ID` replay, per-origin connection ceiling, or concurrent-stream capacity has no coverage.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

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 well-organized, mostly executable skill body that uses tables and code efficiently and offloads advanced recipes to real reference files. Its main weakness is the absence of an explicit validation/retry feedback loop in the workflow narrative.

Suggestions

Add an explicit validation checkpoint in Step 1 or Step 2 (e.g., assert the response Content-Type is text/event-stream and that messages terminate with \n\n before running browser assertions) to strengthen the feedback loop.

Tighten the stream-format example by removing the trailing blank line and condensing the field table descriptions so every token earns its place.

Inline a minimal reconnect/Last-Event-ID assertion snippet or a one-line pointer to the exact recipe section, so the core workflow is actionable end-to-end without a context switch.

DimensionReasoningScore

Conciseness

The body is lean, using tables for stream fields and readyState plus tight code blocks with minimal prose; only minor trims are possible (e.g., redundant blank line in the stream example, slightly verbose field descriptions), so it sits just below fully lean.

4 / 5

Actionability

Two complete, executable Playwright/TypeScript test blocks and a concrete stream-format example make it copy-paste ready for common cases, while advanced recipes (reconnect, retry, connection ceiling) are deferred to references rather than fully inlined.

4 / 5

Workflow Clarity

Steps are clearly sequenced (server-side format → browser test → readyState lifecycle) with assertions acting as implicit checkpoints, but there is no explicit validate→fix→retry feedback-loop narrative, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

The body is a well-signaled overview with one-level-deep references to references/sse-test-recipes.md and references/sse-load.md (both verified to exist), with advanced recipes and load testing appropriately split out and easy to navigate.

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, concrete description that names comprehensive SSE capabilities, explicit trigger conditions, and clear boundaries against sibling skills. It only slightly under-covers a few natural user phrasings for real-time/streaming updates.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full SSE surface — EventSource API, stream format fields, Last-Event-ID replay, content-type, HTTP/1.1 connection-pool limits, and k6 load testing — giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (the SSE surfaces and tooling) and 'when' ('Use when a feature pushes updates over text/event-stream and the reconnect interval, Last-Event-ID replay, per-origin connection ceiling, or concurrent-stream capacity has no coverage').

5 / 5

Trigger Term Quality

Strong natural-keyword coverage with synonyms and tokens ('Server-Sent Events', 'SSE', 'EventSource', 'text/event-stream', 'one-way-streaming'), but a few common user phrasings like 'real-time push' or 'streaming updates' are absent, placing it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Explicitly scopes to one-way push and redirects bidirectional needs to websocket-tests, with grpc-streaming noted as a typed alternative, giving a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents