server-sent-events-setup
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill server-sent-events-setupServer Sent Events Setup - Auto-activating skill for API Integration. Triggers on: server sent events setup, server sent events setup 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, functioning more as a title than a useful skill description. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term and generic category reference provide almost no value for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Implements Server-Sent Events endpoints, configures event streams, handles client reconnection logic, and sets up real-time data push from server to browser.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions SSE, EventSource, server push, real-time streaming, or needs one-way server-to-client communication.'
Add common variations and related terms users might say: 'SSE', 'EventSource API', 'streaming API', 'real-time updates', 'push events', 'text/event-stream'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Server Sent Events Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'configure', 'implement', 'stream', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause explaining scenarios for skill selection. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('server sent events setup' listed twice) and miss common variations users might say like 'SSE', 'event streaming', 'real-time updates', 'push notifications', or 'EventSource'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Server Sent Events' is a specific technology, the vague 'API Integration' category and lack of concrete actions could cause overlap with other API-related skills. The SSE focus provides some distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a template placeholder with no actual content. It describes what a skill should do rather than providing any actionable guidance for implementing Server Sent Events. The entire body consists of meta-descriptions and trigger examples without any technical substance.
Suggestions
Add concrete, executable code examples showing SSE server setup (e.g., Node.js/Express or Python/FastAPI) and client-side EventSource usage
Include a clear workflow: 1) Set up SSE endpoint, 2) Configure headers (Content-Type: text/event-stream), 3) Implement message format, 4) Handle client reconnection
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual technical content
Add specific examples of SSE message format (id, event, data, retry fields) and common patterns like heartbeat/keep-alive
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler text with no actual technical information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-descriptions Claude doesn't need. | 1 / 3 |
Actionability | There is zero executable guidance - no code examples, no commands, no specific steps for implementing SSE. Phrases like 'provides step-by-step guidance' and 'generates production-ready code' describe capabilities without demonstrating them. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for setting up Server Sent Events. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no structure for actual learning. There are no references to detailed documentation, examples, or related files - just self-referential trigger descriptions. | 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
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.