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.mdRedis stream registry with pipeline and sorted set
STREAM_KEY_PREFIX value
0%
100%
ACTIVE_STREAMS_KEY value
0%
100%
COMPLETION_KEY_PREFIX value
0%
100%
STREAM_TTL constant
0%
100%
STALE_THRESHOLD constant
100%
100%
COMPLETION_TTL constant
0%
100%
Pipeline usage in register
62%
100%
Pipeline in heartbeat
50%
100%
Sorted set for heartbeat
0%
100%
zrangebyscore for stale detection
0%
100%
StreamState enum values
0%
100%
Duplicate stream check
50%
100%
Metadata serialization
100%
100%
File structure
0%
0%
SSE endpoint with heartbeat, completion recovery, and headers
Completion check before registration
100%
100%
Recovery response format
100%
100%
Heartbeat interval 15 seconds
100%
100%
Heartbeat SSE comment format
50%
100%
Unregister on disconnect
70%
100%
Content-Type header
100%
100%
Cache-Control header
100%
100%
X-Stream-Id header
0%
100%
Connected event on start
0%
100%
CompletionStore TTL
100%
100%
File placement
0%
80%
Stream guardian cleanup and client-side reconnection
Guardian check interval
0%
100%
Guardian marks ORPHANED
100%
100%
Guardian error handling
0%
100%
Guardian start/stop
75%
100%
Client recovery check first
100%
100%
Client max 3 retries
0%
100%
Exponential backoff delay
40%
100%
EventSource cleanup
100%
100%
Guardian file placement
50%
100%
Only ACTIVE streams flagged
100%
100%
Client hook closes on unmount
100%
100%
3dd3ac0
Table of Contents
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.