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 correctly identifies the JWT exp vs Date.now() unit mismatch bug and provides the correct fix.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Identifies seconds vs milliseconds mismatch",
"description": "Explains that JWT exp is in seconds (Unix timestamp) while Date.now() returns milliseconds",
"max_score": 20
},
{
"name": "Provides correct fix",
"description": "Shows the fix: either divide Date.now() by 1000 or multiply exp by 1000 before comparing",
"max_score": 15
},
{
"name": "Correct comparison direction",
"description": "The fix checks that current time is less than exp (token not yet expired), not the reverse",
"max_score": 10
},
{
"name": "No incorrect information",
"description": "Response does not contain factually wrong statements about JWT, Unix timestamps, or JavaScript Date APIs",
"max_score": 15
}
]
}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