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 refactors a callback-based function to async/await with proper error handling.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Function is async",
"description": "The refactored function uses the async keyword",
"max_score": 12
},
{
"name": "Uses await on db.query",
"description": "Awaits the database query call instead of using a callback",
"max_score": 12
},
{
"name": "Preserves not-found check",
"description": "Still throws or rejects when no rows are returned (the empty result case)",
"max_score": 12
},
{
"name": "Returns the user row",
"description": "Returns rows[0] or equivalent single user result",
"max_score": 10
},
{
"name": "Error propagation via throw or rejection",
"description": "Database errors propagate naturally via async/await (thrown or uncaught) rather than being swallowed",
"max_score": 10
},
{
"name": "No callback parameter in signature",
"description": "The refactored function removes the callback parameter from the function signature",
"max_score": 8
}
]
}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