websocket-realtime

Real-time communication patterns with WebSocket, Socket.io, Server-Sent Events, and scaling strategies

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/websocket-realtime/SKILL.md

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and token-efficient with executable TypeScript examples and a useful checklist, but it functions as a monolithic pattern catalog without a sequenced workflow or progressive file structure.

Suggestions

Add a short "How to choose" decision flow (SSE vs WebSocket vs Socket.io) with validation checkpoints to turn the catalog into a guided workflow.

Move the larger reference examples (multi-server Redis scaling, full reconnection logic) into separate one-level-deep reference files linked from the body.

Dimension	Reasoning	Score
Conciseness	The body is lean executable code with almost no concept explanation Claude already knows; the single prose note on SSE and the bullet lists all earn their place.	3 / 3
Actionability	Each section provides complete, copy-paste-ready TypeScript with real imports and libraries (ws, socket.io, redis-adapter), plus a concrete reconnection class and checklist.	3 / 3
Workflow Clarity	Patterns are organized by section and a verification checklist exists, but the content is a catalog of standalone snippets rather than a sequenced multi-step workflow with explicit error-recovery feedback loops.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~200-line file; sections are well-organized, but large code blocks (scaling, reconnection) that could be split into one-level-deep references remain inline.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 distinctive and uses strong natural trigger terms, but it lacks an explicit "Use when..." trigger clause and describes patterns rather than concrete actions, capping completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when building real-time features like chat, live dashboards, or push notifications with WebSocket, Socket.io, or SSE."

Replace the abstract "communication patterns" framing with concrete actions (e.g. "Build WebSocket servers, manage rooms, scale with Redis adapters, implement SSE streams and client reconnection").

Dimension	Reasoning	Score
Specificity	It names the domain and concrete technologies ("WebSocket, Socket.io, Server-Sent Events, and scaling strategies") but describes patterns/strategies rather than listing multiple specific concrete actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It clearly states what the skill covers but has no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"WebSocket", "Socket.io", "Server-Sent Events", and "real-time communication" are exactly the natural terms a user would say when needing this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The real-time web-communication niche with named technologies (WebSocket, Socket.io, SSE) is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/awesome-claude-code-toolkit
Path: skills/websocket-realtime/SKILL.md
Commit: ebdf1d5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.