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
You are working in a Tessl project. The repository root has a tessl.json with
no schedules block yet.
The user says:
Please schedule the dependency digest to run every weekday morning at 8am UTC. The skill is
tessleng/dependency-digestand it should use thedependency-digestenvironment.
Add a repo-defined schedule to tessl.json that matches this request, then
validate it.
schedules block schema (the required
fields are skill, cron, and environment).tessl schedule validate from the repo root and make sure it passes.Write a short note of what you did to result.md.
tessl.json: updated with a valid schedules block containing the new entryresult.md: a brief note with the schedule key, the cron you wrote, and the
result of tessl schedule validateThe following files are provided as inputs. Extract them before beginning.
=============== FILE: tessl.json =============== { "name": "acme/reports", "mode": "project", "dependencies": { "tessleng/dependency-digest": { "version": "0.1.0" } } }