sse-resilience
Redis-backed SSE stream management with stream registry, heartbeat monitoring, completion store for terminal events, and automatic orphan cleanup via background guardian process.
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill sse-resilience81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 1.90xAgent success when using this skill
Validation for skill structure
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at technical specificity and carves out a distinct niche, but critically lacks trigger guidance ('Use when...') that would help Claude know when to select this skill. The technical jargon may also miss users who describe their needs in more common terms like 'real-time events' or 'server-sent events'.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when implementing real-time event streaming, managing SSE connections, or building Redis-backed pub/sub systems.'
Include natural language variations users might say: 'server-sent events', 'real-time streaming', 'event broadcasting', 'stream lifecycle management'.
Add file extension or technology markers if applicable, e.g., 'Redis streams', 'EventSource API', to improve trigger matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'SSE stream management', 'stream registry', 'heartbeat monitoring', 'completion store for terminal events', and 'automatic orphan cleanup via background guardian process'. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes technical terms like 'Redis', 'SSE', 'heartbeat', 'stream registry' that developers might use, but missing common variations users might say like 'server-sent events', 'real-time streaming', 'event streams', or 'pub/sub'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Redis + SSE + stream management with guardian process - unlikely to conflict with other skills due to the unique combination of technologies and features. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable code for SSE stream resilience with Redis backing. Its main strengths are actionability and complete implementations. However, it could be more concise by removing explanatory sections, and would benefit from explicit integration steps with validation checkpoints rather than just presenting the code components.
Suggestions
Add an explicit integration workflow section with numbered steps: 1) Set up Redis connection, 2) Initialize registry/store, 3) Start guardian, 4) Verify with test stream - including validation commands at each step
Move the detailed class implementations to a separate REFERENCE.md file, keeping only the SSE endpoint and client hook in the main skill with links to the full implementations
Remove or condense the 'When to Use This Skill' and 'Core Concepts' sections - the code itself demonstrates the concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When to Use This Skill' that explain problems Claude can infer. The ASCII diagram and 'Core Concepts' section add modest value but could be trimmed. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete class implementations, SSE endpoint, and client-side React hook. Code is copy-paste ready with proper imports and realistic patterns. | 3 / 3 |
Workflow Clarity | The implementation shows the components but lacks explicit step-by-step integration workflow. No validation checkpoints for verifying Redis connection, testing heartbeat mechanism, or confirming guardian is running correctly. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is monolithic with ~200 lines of code inline. The 'Related Patterns' section references other files but the main implementation could benefit from splitting into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 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.