building-websocket-server
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill building-websocket-serverBuild 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is a generic API template that has been superficially adapted for WebSocket servers without any WebSocket-specific guidance. It lacks executable code, concrete WebSocket protocols, connection handling patterns, or real-time communication specifics. The content reads as boilerplate filler rather than actionable instruction.
Suggestions
Add concrete WebSocket code examples showing connection establishment, message handling, and broadcast patterns (e.g., using ws library for Node.js or websockets for Python)
Include WebSocket-specific workflow steps: connection handshake, message framing, heartbeat/ping-pong, graceful disconnection, and reconnection handling
Remove generic filler text and duplicate overview sentences; focus on what makes WebSocket servers different from REST APIs
Add validation checkpoints for WebSocket-specific concerns: connection limits, message size validation, authentication during upgrade request
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains significant filler content like 'This skill provides automated assistance for websocket server builder tasks' repeated twice, generic prerequisites that Claude already knows, and verbose boilerplate that doesn't add value specific to WebSocket servers. | 1 / 3 |
Actionability | No executable code examples for WebSocket implementation. Instructions are vague ('Generate boilerplate code', 'Implement endpoint handlers') without concrete WebSocket-specific commands, connection handling, or message protocols. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbering (two separate lists both starting at 1), no validation checkpoints for WebSocket connections, and missing critical WebSocket-specific workflow elements like connection lifecycle management or heartbeat handling. | 1 / 3 |
Progressive Disclosure | References external files (implementation.md, errors.md, examples.md) which is appropriate structure, but the main content is poorly organized and the references feel like placeholders rather than well-signaled navigation to specific content. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
90%This is a solid skill description with excellent trigger terms and completeness. The main weakness is the lack of specific concrete actions beyond the high-level 'build scalable WebSocket servers' - it would benefit from listing specific capabilities like connection management, message broadcasting, or room/channel support.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Build scalable WebSocket servers with connection management, message broadcasting, room/channel support, and heartbeat handling.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WebSocket servers) and mentions 'real-time bidirectional communication' and 'scalable', but lacks specific concrete actions like connection handling, message broadcasting, authentication, or heartbeat management. | 2 / 3 |
Completeness | Clearly answers both what ('Build scalable WebSocket servers for real-time bidirectional communication') and when ('Use when enabling real-time bidirectional communication' plus explicit trigger phrases). Has explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger phrases users would say: 'build WebSocket server', 'add real-time API', 'implement WebSocket'. These are practical terms developers would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | WebSocket is a specific protocol with distinct terminology. The triggers 'WebSocket server', 'real-time API', and 'implement WebSocket' are unlikely to conflict with other skills like general HTTP APIs or database skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
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.