Compressed caveman-style prose for AI coding agents — cuts ~65% output tokens while keeping full technical accuracy
96
100%
Does it follow best practices?
Impact
96%
1.00xAverage score across 38 eval scenarios
Passed
No known issues
{
"context": "Tests whether the response provides a robust WebSocket reconnection design.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Implements exponential backoff",
"description": "Reconnection delays increase exponentially (e.g., 1s, 2s, 4s, 8s...) with a maximum cap",
"max_score": 15
},
{
"name": "Adds jitter to backoff",
"description": "Adds randomized jitter to prevent all clients reconnecting simultaneously after server restart",
"max_score": 8
},
{
"name": "Handles missed message recovery",
"description": "Describes a mechanism to catch up on missed data after reconnection (last-event-id, sequence numbers, timestamp-based replay, or full state sync)",
"max_score": 12
},
{
"name": "Detects connection loss",
"description": "Uses onclose/onerror handlers and optionally heartbeat/ping-pong to detect stale connections",
"max_score": 10
},
{
"name": "No incorrect information",
"description": "WebSocket API usage is correct and the reconnection logic is sound",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37