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 is a very weak description that essentially just restates the skill name without providing any concrete capabilities, natural trigger terms, or explicit usage guidance. It reads like an auto-generated template with no meaningful content filled in. The duplicate trigger term and lack of any actionable detail would make it nearly impossible for Claude to reliably select this skill from a pool of similar API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures Server-Sent Events (SSE) endpoints, implements EventSource clients, handles reconnection logic, and sets up event stream parsing.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks about SSE, EventSource, real-time server push, streaming HTTP responses, or one-way server-to-client event streams.'
Include common variations and related terms users might use: 'SSE', 'EventSource API', 'real-time updates', 'text/event-stream', 'streaming events' to improve trigger term coverage.
| 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 there is no 'Use when...' clause with explicit triggers. | 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 | While 'Server Sent Events' is a somewhat specific technology, the description's vagueness and the broad 'API Integration' category label could cause overlap with other API-related skills. The mention of SSE does provide some niche specificity. | 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 technical content about Server Sent Events. It consists entirely of meta-descriptions and trigger phrases, providing zero actionable guidance, code examples, or workflow instructions. It would need to be completely rewritten with actual SSE implementation details to be useful.
Suggestions
Add concrete, executable code examples for SSE setup (e.g., server-side EventSource endpoint in Node.js/Python, client-side EventSource connection, handling reconnection and error events).
Include a clear workflow: 1) Set up SSE endpoint, 2) Configure headers (Content-Type: text/event-stream, etc.), 3) Implement client listener, 4) Test connection with validation steps.
Replace all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') with actual technical content covering SSE message format, retry logic, and common pitfalls.
Add references to related patterns (e.g., comparison with WebSockets, fallback strategies) or link to detailed guides for advanced SSE topics like custom event types and authentication.
| 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 configuration examples, no API patterns. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is present. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or error handling 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, examples, or related documentation. | 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
b8a3b3e
- 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.