Cron jobs for Node.js applications that enables developers to execute functions or system commands on schedules defined using standard cron syntax
94
Pending
Does it follow best practices?
Impact
94%
1.20xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "This criteria evaluates the engineer's ability to use the cron package's next execution time query capabilities, specifically the methods for retrieving upcoming execution times, calculating time until execution, and accessing job history.",
"type": "weighted_checklist",
"checklist": [
{
"name": "sendAt() or nextDate()",
"description": "Uses sendAt() standalone function or CronJob.nextDate() method to get the next execution time for a cron expression",
"max_score": 25
},
{
"name": "nextDates() usage",
"description": "Uses CronJob.nextDates(count) method or multiple sendAt() calls to retrieve multiple upcoming execution times (specifically 5 times as required)",
"max_score": 25
},
{
"name": "timeout() or calculation",
"description": "Uses timeout() standalone function or calculates milliseconds until next execution using sendAt() or nextDate() with current time",
"max_score": 20
},
{
"name": "lastDate() usage",
"description": "Uses CronJob.lastDate() method to retrieve the last execution time from an active job object",
"max_score": 15
},
{
"name": "CronJob or CronTime",
"description": "Creates CronJob or CronTime instances appropriately to work with cron expressions and timing queries",
"max_score": 10
},
{
"name": "Timezone support",
"description": "Properly passes timezone parameter to CronJob or CronTime constructor to handle timezone-aware scheduling",
"max_score": 5
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10