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
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 ./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 specificity and distinctiveness, clearly naming a narrow technical domain with concrete components. However, it completely lacks trigger guidance ('Use when...') which is critical for Claude to know when to select this skill. The technical jargon, while precise, may not match how users naturally phrase requests.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when implementing or debugging SSE streaming, managing server-sent event connections, or handling Redis pub/sub stream lifecycle.'
Include natural language trigger terms users might say, such as 'server-sent events', 'streaming connections', 'real-time event delivery', or 'stream disconnection handling'.
| 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 (Redis-backed SSE stream management with various features) but completely lacks any 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'when' is so absent it warrants a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Redis', 'SSE', 'stream', 'heartbeat', 'orphan cleanup', but these are fairly technical. Missing common user-facing variations like 'server-sent events', 'streaming', 'real-time events', or 'event stream'. Users might not naturally say 'guardian process' or 'completion store'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Redis, SSE streams, heartbeat monitoring, completion store, and orphan cleanup via guardian process is highly specific and unlikely to conflict with other skills. This is a clear, narrow niche. | 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 high-quality, executable TypeScript code for a Redis-backed SSE resilience system with good coverage of registry, completion store, guardian, endpoint, and client recovery. However, it's overly monolithic—all implementation details are inline rather than referenced—and lacks explicit integration/validation workflow steps. Some sections (When to Use, Common Mistakes) add verbosity without proportional value.
Suggestions
Extract the full class implementations into a referenced file (e.g., IMPLEMENTATION.md) and keep only the key interfaces, usage patterns, and integration steps in the main SKILL.md.
Add an explicit integration workflow with validation checkpoints, e.g.: 1. Verify Redis connection, 2. Register stream and confirm, 3. Verify heartbeat updates, 4. Test completion storage/recovery, 5. Confirm guardian cleanup.
Remove or condense the 'When to Use This Skill' and 'Common Mistakes' sections—they restate information Claude can infer from the implementation itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial executable code which is valuable, but includes some unnecessary sections like 'When to Use This Skill' and 'Core Concepts' that explain things Claude already understands. The 'Common Mistakes' section largely restates the best practices in negative form. The code itself is reasonably lean but the overall document could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with complete class implementations, SSE endpoint handler, and client-side React hook. Code is copy-paste ready with concrete Redis key patterns, TTL values, and pipeline operations. | 3 / 3 |
Workflow Clarity | The architecture diagram and code show the flow between components, but there's no explicit step-by-step integration workflow. There are no validation checkpoints for verifying Redis connectivity, confirming stream registration succeeded, or testing the guardian process. For a system involving background cleanup of potentially orphaned resources, explicit verification steps would be important. | 2 / 3 |
Progressive Disclosure | The document is a monolithic file with all implementation details inline (~250 lines of code). The 'Related Patterns' section references other files but the core content could benefit from splitting the full class implementations into separate reference files, keeping only key patterns and usage examples in the main skill file. | 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-data
- Commit
3dd3ac0
- 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.