Create and migrate repo-defined Tessl schedules in a project's tessl.json. Turns a plain-language cadence into a validated schedules entry, and moves an existing UI/CLI schedule into version control.
90
97%
Does it follow best practices?
Impact
94%
0.94xAverage score across 2 eval scenarios
Low
Low-risk findings worth noting
{
"context": "Tests whether the agent turns a plain-language cadence into a valid repo-defined schedule entry in tessl.json: correct five-field cron for 'every weekday morning at 8am UTC', the three required fields, a kebab-case key, and a passing `tessl schedule validate`.",
"type": "weighted_checklist",
"checklist": [
{
"name": "schedules block added",
"description": "tessl.json now has a top-level `schedules` object containing one new entry, and the rest of the original file (name, mode, dependencies) is preserved.",
"max_score": 15
},
{
"name": "Correct cron for weekdays 8am",
"description": "The entry's `cron` is a five-field expression that fires at 08:00 on weekdays, e.g. `0 8 * * 1-5` (equivalently `0 8 * * MON-FRI`). It is not per-minute and not a wrong time.",
"max_score": 25
},
{
"name": "Required fields correct",
"description": "The entry has `skill` set to `tessleng/dependency-digest`, `environment` set to `dependency-digest` (the environment name, not an id), and the `cron` above. No misspelled or unknown field names are present (the schema is strict).",
"max_score": 25
},
{
"name": "Valid kebab-case key",
"description": "The schedule's map key is a lowercase kebab-case slug (a-z, 0-9, single dashes), derived from the job (e.g. `dependency-digest` or `weekday-dependency-digest`).",
"max_score": 10
},
{
"name": "Validation run and passing",
"description": "The agent ran `tessl schedule validate` (from the repo root) and result.md reports that it passed.",
"max_score": 15
},
{
"name": "Did not ask user for a cron",
"description": "The agent derived the cron itself from the plain-language cadence rather than asking the user to supply a cron expression.",
"max_score": 10
}
]
}