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 diagnoses a CORS preflight failure beyond just the Allow-Origin header.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Explains the preflight (OPTIONS) request",
"description": "Explains that the browser sends an OPTIONS preflight request before the actual POST, and the server must respond to it correctly",
"max_score": 12
},
{
"name": "Identifies missing Allow-Headers",
"description": "Points out that Content-Type: application/json triggers a preflight that requires Access-Control-Allow-Headers to include Content-Type",
"max_score": 15
},
{
"name": "Mentions Allow-Methods needed",
"description": "Notes that Access-Control-Allow-Methods must include POST",
"max_score": 10
},
{
"name": "Server must handle OPTIONS method",
"description": "Notes that the server must respond to the OPTIONS request with a 200/204 and the CORS headers (not just add headers to POST responses)",
"max_score": 10
},
{
"name": "No incorrect information",
"description": "CORS mechanism explanation is technically correct",
"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