websocket-engineer
tessl i github:jeffallan/claude-skills --skill websocket-engineerUse when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.
Validation
75%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
Implementation
42%The skill has strong organizational structure with good progressive disclosure through its reference table, but critically lacks actionable code examples. It reads more like a checklist of considerations than executable guidance. The persona/role framing wastes tokens, and the constraints section tells Claude what to do without showing how.
Suggestions
Add executable Socket.IO server setup code showing connection handling, authentication, and room management
Include a concrete client-side connection example with reconnection logic
Add a Redis adapter configuration example for horizontal scaling
Remove the role definition section and persona backstory - these waste tokens without adding actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('Senior WebSocket specialist with 10+ years...') and the role definition section adds little value since Claude doesn't need persona backstory. However, the constraints and reference sections are reasonably efficient. | 2 / 3 |
Actionability | The skill lacks any concrete, executable code examples. It describes what to do ('Implement automatic reconnection with exponential backoff') but never shows how. No Socket.IO setup code, no event handler examples, no client connection code - just abstract guidance. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a sequence but lacks validation checkpoints. For WebSocket systems involving connection state and scaling, there are no explicit verification steps (e.g., 'test connection before deploying', 'verify Redis pub/sub is working'). | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to specific topics (protocol, scaling, patterns, security, alternatives). References are one level deep and well-signaled with clear 'Load When' guidance. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
N/ASomething went wrong
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.