docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "This evaluation assesses how well the engineer uses the cli package's color output control and TTY detection capabilities. The focus is on properly utilizing status message methods, respecting color control flags, and handling debug mode.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Status message methods",
"description": "Uses cli.info(), cli.error(), cli.ok(), and cli.debug() methods to display status messages with appropriate color coding",
"max_score": 25
},
{
"name": "Status plugin",
"description": "Enables the status plugin using cli.enable('status') to access --debug and --no-color flags",
"max_score": 15
},
{
"name": "Argument parsing",
"description": "Calls cli.parse() to parse command-line arguments and enable flag recognition",
"max_score": 10
},
{
"name": "No-color handling",
"description": "Properly respects the --no-color flag automatically handled by the cli package to disable colored output",
"max_score": 20
},
{
"name": "Debug mode",
"description": "Debug messages are displayed when --debug flag is provided and hidden when not provided, leveraging cli.debug() behavior",
"max_score": 15
},
{
"name": "Message content",
"description": "Status messages display the correct information (CPU usage, memory status, operational status) as specified in the test cases",
"max_score": 10
},
{
"name": "API compliance",
"description": "Exports the reportStatus function with the correct signature that accepts a metrics object with cpu, memory, and status properties",
"max_score": 5
}
]
}