building-websocket-server

Build scalable WebSocket servers for real-time bidirectional communication. Use when enabling real-time bidirectional communication. Trigger with phrases like "build WebSocket server", "add real-time API", or "implement WebSocket".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The content is well-organized and lean with good progressive disclosure to real reference files, but the main body offers descriptive instructions without executable code and the workflow lacks explicit validation checkpoints.

Suggestions

Add one minimal executable code snippet (e.g., a ws server upgrade + JWT handshake stub) so the main body is copy-paste ready rather than delegating all code to references.

Insert an explicit validation checkpoint in the instructions, such as verifying the upgrade handshake authenticates before proceeding and re-testing after each lifecycle step.

Replace or supplement the prose Examples with a short concrete code excerpt so examples demonstrate rather than describe.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what a WebSocket is or how libraries work — with concrete prerequisites and a compact error table where every token earns its place, matching the level-3 anchor.	3 / 3
Actionability	Instructions are specific (e.g., '/ws', '/socket.io' paths, close code 1008, default 30s heartbeat, Redis pub/sub) but the body contains no executable code — it delegates code to references — so it falls short of the level-3 'copy-paste ready' anchor and lands at 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The nine numbered instructions give a clear sequence, but there are no explicit validate-then-proceed checkpoints or fix-retry feedback loops within the workflow, matching the level-2 anchor of 'steps listed but validation gaps'.	2 / 3
Progressive Disclosure	The body is a concise overview pointing one level deep to real, clearly-signaled references ('See ${CLAUDE_SKILL_DIR}/references/implementation.md', errors.md, examples.md), with content appropriately split, matching the level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 clearly answers what the skill does and when to use it, with natural trigger phrases and a distinct niche. Its only weakness is specificity: it names a single broad action rather than enumerating multiple concrete capabilities.

Suggestions

List multiple concrete actions (e.g., connection lifecycle management, room/channel subscriptions, heartbeat keepalive, Redis pub/sub scaling) instead of the single 'build scalable WebSocket servers' action to raise specificity.

Dimension	Reasoning	Score
Specificity	Quotes 'Build scalable WebSocket servers for real-time bidirectional communication' name a clear domain and one concrete action, but only a single action rather than the multiple specific actions (e.g., extract/fill/merge) the level-3 anchor requires.	2 / 3
Completeness	It explicitly states what ('Build scalable WebSocket servers for real-time bidirectional communication') and when ('Use when enabling real-time bidirectional communication'), with explicit trigger phrases, matching the level-3 anchor for both what and when.	3 / 3
Trigger Term Quality	Quotes "build WebSocket server", "add real-time API", and "implement WebSocket" are natural phrases a user would say, matching the level-3 anchor for good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	WebSocket servers occupy a clear niche with distinct triggers unlikely to conflict with other skills, matching the level-3 anchor for a clear niche with distinct triggers.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

Reviewed: 1 day 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.