server-sent-events-setup
Server 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.
35
3%
Does it follow best practices?
Impact
92%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/server-sent-events-setup/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a template placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures Server-Sent Events (SSE) endpoints, implements EventSource clients, handles reconnection logic, and parses event streams.'
Add a 'Use when...' clause with natural trigger terms like 'SSE', 'EventSource', 'event stream', 'real-time server push', 'streaming updates', 'text/event-stream'.
Remove the duplicate trigger term and replace with diverse natural language variations users would actually use when requesting help with SSE.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the topic 'Server Sent Events Setup' without describing any concrete actions. There are no specific capabilities listed such as 'configure SSE endpoints', 'handle event streams', or 'implement reconnection logic'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and provides no meaningful 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name and doesn't constitute explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'server sent events setup' repeated twice. Missing natural variations users would say like 'SSE', 'event stream', 'real-time updates', 'EventSource', 'streaming API', or 'push notifications'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Server Sent Events' is a somewhat specific technology, which provides some distinctiveness. However, the vague 'API Integration' category and lack of concrete actions could cause overlap with other API-related skills like WebSocket or general streaming skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content about Server Sent Events. It consists entirely of boilerplate meta-descriptions that repeat the skill name without providing any technical guidance, code examples, or actionable instructions. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for both server-side SSE implementation (e.g., Node.js/Express or Python/Flask) and client-side EventSource usage.
Include a clear workflow: 1) Set up SSE endpoint, 2) Configure headers (Content-Type: text/event-stream, etc.), 3) Implement client connection, 4) Test with curl or browser.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content covering SSE message format, reconnection handling, and error scenarios.
Add specific guidance on SSE vs WebSockets trade-offs, connection limits, and production considerations like load balancer timeouts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Server Sent Events. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific SSE implementation details, no examples of EventSource usage, no server-side setup. It only describes what it could do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive block with no meaningful structure. Sections exist but contain no substantive content and there are no references to detailed materials or external files. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.