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 Docker DNS issues as distinct from host DNS.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Identifies Docker DNS isolation",
"description": "Explains that Docker containers have their own DNS configuration, separate from the host's resolv.conf",
"max_score": 15
},
{
"name": "Suggests checking container DNS config",
"description": "Recommends checking /etc/resolv.conf inside the container or docker run --dns settings",
"max_score": 12
},
{
"name": "Mentions Docker's embedded DNS (127.0.0.11)",
"description": "References Docker's internal DNS server at 127.0.0.11 for user-defined networks or the default DNS behavior",
"max_score": 10
},
{
"name": "Provides debugging commands",
"description": "Suggests practical debugging steps: nslookup/dig inside container, docker inspect for DNS settings, checking Docker network configuration",
"max_score": 10
},
{
"name": "No incorrect information",
"description": "DNS and Docker networking concepts are 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