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.
81
Quality
57%
Does it follow best practices?
Impact
97%
1.90xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/api/sse-resilience-dadbodgeoff-drift/SKILL.mdQuality
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 for when Claude should use this skill. The technical jargon may also miss users who describe their needs in simpler terms like 'real-time events' or 'streaming connections'.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when implementing real-time streaming, managing SSE connections, or building event-driven systems with Redis'
Include natural language variations users might say: 'server-sent events', 'real-time updates', 'event streaming', 'connection monitoring'
| 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' that developers would use, but missing common variations or simpler terms users might say like 'server-sent events', 'real-time streaming', or 'event streams'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Redis, SSE, and 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 strength is actionability - the TypeScript implementations are complete and production-ready. However, it could be more concise by removing explanatory sections, and would benefit from clearer workflow guidance for integrating these components together.
Suggestions
Remove or condense the 'When to Use This Skill' section - these are obvious use cases Claude would infer
Add an explicit setup/integration workflow: 1. Configure Redis connection 2. Initialize registry/store 3. Start guardian 4. Verify with test stream
Consider splitting the large implementation section into referenced files (e.g., STREAM_REGISTRY.md, CLIENT_RECOVERY.md) with just the core pattern in SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When to Use This Skill' that explain obvious use cases Claude would understand. The ASCII diagram and some explanatory text could be trimmed. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete class implementations, SSE endpoint, and client-side hook. Code is copy-paste ready with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | The multi-component system is presented but lacks explicit validation checkpoints. No clear sequence for setup/deployment, and the relationship between components (when to start guardian, how to verify Redis connection) is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the implementation section is quite long (could benefit from splitting into separate files). References to related patterns at the end are good but the main content is somewhat monolithic. | 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 | |
- Repository
- majiayu000/claude-skill-registry
- Commit
6213d1a
- 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.