Tessl • The package manager for agent skills

SkillPublic

bun-websocket-server

This skill should be used when the user asks about "WebSocket in Bun", "real-time communication", "Bun.serve websocket", "ws server", "socket connections", "pub/sub", "broadcasting messages", "WebSocket upgrade", or building real-time applications with Bun.

Quality

80%

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/bun/skills/bun-websocket-server/SKILL.md

Quality

Content

72%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.

The body is a highly actionable, executable Bun WebSocket reference with strong code coverage and lean prose. Its gaps are the absence of a sequenced workflow with validation checkpoints and progressive-disclosure issues: a large inline reference that should be split out, plus references pointing to missing files.

Suggestions

Move the detailed WebSocket Options and handler reference into `references/` files and keep SKILL.md as a concise overview with one-level-deep links, which also resolves the missing-file issue.

Create the referenced `references/compression.md` and `references/scaling.md` (or remove the dangling references) so signaled navigation is not broken.

Add a short validation/backpressure feedback loop (e.g., check `ws.send` return value, wait for `drain` before resuming) to give the fragile send path an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy with minimal prose and does not explain concepts Claude already knows, but Quick Start overlaps the Handlers section and several example blocks repeat similar upgrade boilerplate, leaving minor trimming opportunities.	4 / 5
Actionability	Copy-paste-ready TypeScript examples cover the common cases comprehensively: quick start, handlers, sending (text/JSON/binary/compressed), pub/sub, broadcasting, server-level publish, auth, and a chat-room pattern.	5 / 5
Workflow Clarity	Content is organized as a feature catalog with no sequenced multi-step workflow or validation checkpoints; while not a destructive task, there are no feedback loops (e.g., verify upgrade succeeded, handle backpressure before resuming send) for fragile operations like backpressure and auth.	3 / 5
Progressive Disclosure	Sections are headed and a "When to Load References" section signals references, but ~350 lines of inline handler/option reference could live in separate files, and the referenced `references/compression.md` and `references/scaling.md` files do not exist in the bundle.	3 / 5
	Total	15 / 20 Passed

Description

81%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.

The description is a strong, trigger-phrase-rich statement with excellent distinctiveness and a clear "when to use" clause. Its main weakness is that it lists domain topics rather than the concrete actions the skill performs, leaving the "what" somewhat implicit.

Suggestions

Lead with the concrete actions the skill performs (e.g., "Build WebSocket servers with Bun.serve, handle upgrades, broadcast and pub/sub messages") before the trigger list, so "what" is explicit rather than implied.

Keep the existing trigger-phrase list but ensure the opening clause uses third-person capability verbs ("Builds", "Implements") instead of "This skill should be used when..." to make the "what" unambiguous.

Dimension	Reasoning	Score
Specificity	Names the WebSocket-in-Bun domain and surfaces concrete sub-features ("WebSocket upgrade", "pub/sub", "broadcasting messages") but never states the concrete actions the skill performs, so it sits at the lower edge of comprehensive coverage.	3 / 5
Completeness	An explicit "This skill should be used when the user asks about..." clause answers "when" clearly, but the "what" is only implied by the domain rather than stated as concrete verbs, keeping it just below a fully explicit what-and-when anchor.	4 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms and the specific API surface ("WebSocket in Bun", "Bun.serve websocket", "ws server", "pub/sub", "broadcasting messages", "WebSocket upgrade") that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Narrow Bun-WebSocket niche with distinct, specific triggers ("Bun.serve websocket", "WebSocket upgrade") that minimize overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/bun/skills/bun-websocket-server/SKILL.md
Revision: 8837836

Reviewed: 20 days ago

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.

bun-websocket-server

Table of Contents

Is this your skill?