CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/graphql-subscription-test-author

Authors GraphQL subscription resolver test suites over graphql-ws (WebSocket) and graphql-sse (Server-Sent Events) transports: subscribe to event streams via the async-iterator API, assert emitted data shape and sequence, verify connection lifecycle and protocol close codes, and validate auth-on-connect (connectionParams / authenticate callback) plus resolver-level pubsub trigger logic. Use for real-time subscription operations; not for queries or mutations - for those use apollo-server-tests or graphql-yoga-tests (Mercurius in its references).

72

Quality

90%

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

86%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-structured, actionable skill body with executable examples for both transports and clean one-level-deep progressive disclosure. Slight verbosity in the spec/background sections and absence of an explicit test-failure feedback loop are the only weak spots.

Suggestions

Trim the Overview's restatement of the GraphQL spec subscription execution model and the 'Parsing results' re-explanation of the iterate() result shape — Claude already knows these.

Add a short validate→fix→retry loop in the workflow for when a subscription test hangs or emits an unexpected errors payload (e.g. check errors, inspect close code, adjust retryAttempts).

DimensionReasoningScore

Conciseness

Mostly efficient with copy-paste code and a tight anti-patterns table, but the Overview/'Parsing results' sections restate the spec execution model and iterate() result shape that Claude largely already knows.

4 / 5

Actionability

Fully executable guidance across both transports — install commands, complete TypeScript test snippets, jest config, and CI YAML — covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

A clear 7-step 'How to use' sequence with checkpoints (check errors before data, dispose/close in afterAll, forceExit in CI), but no explicit validate→fix→retry feedback loop for failing tests.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with four clearly-signaled, one-level-deep reference files (transport-server-setup, auth-on-connect, lifecycle-and-close-codes, resolver-and-filter-tests), no nested references, content appropriately split.

5 / 5

Total

18

/

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, specific description that concretely enumerates capabilities and gives explicit use-when guidance plus scope boundaries against sibling skills. Minor keyword-synonym gaps keep trigger quality just below perfect.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'subscribe to event streams via the async-iterator API', 'assert emitted data shape and sequence', 'verify connection lifecycle and protocol close codes', 'validate auth-on-connect ... plus resolver-level pubsub trigger logic' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Authors GraphQL subscription resolver test suites ...') and when ('Use for real-time subscription operations; not for queries or mutations') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('GraphQL subscription', 'real-time subscription operations', 'graphql-ws', 'graphql-sse'), but missing a few common synonyms users might say (e.g. 'WebSocket subscriptions', 'event stream testing').

4 / 5

Distinctiveness Conflict Risk

Clear niche (subscriptions over WS/SSE) with explicit scope exclusion ('not for queries or mutations') and pointer to sibling skills, giving 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents