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

73%

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 ./plugins/api-development/websocket-server-builder/skills/building-websocket-server/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

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 with clean progressive disclosure to real reference files and specific technical guidance. Its weaknesses are the lack of executable code in the body, end-loaded rather than interspersed validation, and some non-essential Output/Resources sections that add tokens.

Suggestions

Add a short executable code snippet (e.g., a minimal ws server setup with upgrade handling) in the Instructions so the body is copy-paste ready rather than deferring all code to implementation.md.

Insert explicit validation checkpoints into the build sequence (e.g., verify the handshake auth rejects unauthorized upgrades before proceeding to room logic) instead of relying solely on the terminal test step.

Trim the speculative Output file listing and the Resources links to well-known documentation, keeping only tokens that directly aid execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence with no concept-padding, but the speculative Output file listing (7 paths) and Resources section of well-known links add tokens that do not all earn their place, matching the score-2 anchor of being mostly efficient but could be tightened.	2 / 3
Actionability	Guidance is concrete and specific (JSON envelope fields, close codes 1008/1006, default 30s heartbeat, upgrade paths), but the body contains no executable code or commands—implementation is deferred to implementation.md—matching the score-2 anchor of concrete guidance that is incomplete without copy-paste-ready code.	2 / 3
Workflow Clarity	The nine instructions are clearly sequenced with a terminal test step and an error-recovery table, but validation checkpoints are end-loaded rather than interspersed, with no explicit verify-then-proceed gates mid-process, matching the score-2 anchor of a present sequence with missing or implicit checkpoints.	2 / 3
Progressive Disclosure	The body is a clear overview with well-signaled one-level-deep references to implementation.md, errors.md, and examples.md, all verified to exist as real bundle files, matching the score-3 anchor.	3 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 well-structured with explicit what/when guidance and natural trigger phrases, giving it a clear niche. Its only weakness is specificity, as it describes a single high-level action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names a concrete action and domain ("Build scalable WebSocket servers for real-time bidirectional communication") but lists only a single action rather than multiple specific concrete actions, matching the score-2 anchor of naming domain and some actions without being comprehensive.	2 / 3
Completeness	It clearly answers both what ("Build scalable WebSocket servers...") and when ("Use when enabling real-time bidirectional communication") with explicit trigger phrases, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Explicit trigger phrases "build WebSocket server", "add real-time API", and "implement WebSocket" are natural terms a user would actually say when needing this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The WebSocket-server niche is specific with distinct triggers, making it clearly distinguishable and unlikely to fire for the wrong skill.	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
Path: plugins/api-development/websocket-server-builder/skills/building-websocket-server/SKILL.md
Commit: 8585d6d

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.