Schedule Management Tile

Two skills for managing repo-defined schedules, recurring launch runs declared in a project's tessl.json instead of created ad hoc in the UI or CLI. A repo-defined schedule is reviewed and version-controlled next to the code it runs against.

Skills

• schedule-setup: Create a schedule from a plain-language description of what to run and how often. The skill can also author a repo-local skill with pinned credential checks for the Linear, Slack, and Notion providers it uses. It writes a readable schedule when possible, adds the schedules block to tessl.json with what runs under each entry's action, validates it, and explains what happens on push.
• schedule-migrate: Move an existing UI- or CLI-created schedule into tessl.json. The skill reads the live schedule's config, writes the equivalent file entry, validates it, and optionally deletes the old schedule once the repo-defined one is confirmed.

How repo-defined schedules work

1. You commit a schedules block to tessl.json and push to the repo's default branch.
2. Tessl's GitHub App sees the push, reads the file, and reconciles the schedules block against the workspace.
3. Each entry becomes an active schedule that fires a launch run on its cron.

Both skills use tessl schedule validate as the local check before you push. It catches shape, cron, and interval problems that the file can be rejected for at apply time.