Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill websocket-client-creatorWebsocket Client Creator - Auto-activating skill for API Integration. Triggers on: websocket client creator, websocket client creator Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mainly of the skill name repeated as trigger terms and a generic category label. It provides no concrete actions, no natural user keywords, and no guidance on when to use it. Claude would struggle to appropriately select this skill from a list of alternatives.
Suggestions
Add specific actions the skill performs, e.g., 'Creates websocket client connections, handles message sending/receiving, manages connection lifecycle and reconnection logic'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user needs to connect to websocket APIs, establish real-time connections, or work with ws:// or wss:// endpoints'
Add common user phrases and file/protocol references like 'websocket', 'ws://', 'wss://', 'real-time', 'streaming connection', 'socket client'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Websocket Client Creator') without describing any concrete actions. There are no specific capabilities listed like 'create connections', 'handle messages', or 'manage reconnection logic'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Only states it's for 'API Integration' which is too vague. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('websocket client creator, websocket client creator'). Missing natural user terms like 'websocket', 'ws://', 'real-time connection', 'socket connection', or 'streaming API'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'websocket' is somewhat specific, the lack of detail means it could conflict with general API skills or HTTP client skills. The category 'API Integration' is broad and doesn't help distinguish it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do without providing any concrete guidance on websocket client creation - no connection code, no event handling patterns, no error handling, no examples of message formats or protocols.
Suggestions
Add executable code examples showing how to create a websocket client connection (e.g., using Python's websockets library or JavaScript's WebSocket API)
Include concrete examples of handling websocket events: onopen, onmessage, onerror, onclose with actual code
Provide a clear workflow for websocket client implementation: connection setup, authentication if needed, message handling, reconnection logic, and graceful shutdown
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with specific, actionable content about websocket protocols and patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of websocket client implementation. The content only describes what the skill supposedly does without actually teaching how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for creating websocket clients. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no code examples to link to, and no organization beyond generic section headers that contain no useful content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.