CtrlK
BlogDocsLog inGet started
Tessl Logo

tessleng/schedule-management

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

0.94x
Quality

97%

Does it follow best practices?

Impact

94%

0.94x

Average score across 2 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-1/

Create a repo-defined schedule from a plain-language request

Problem/Feature Description

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-digest and it should use the dependency-digest environment.

Add a repo-defined schedule to tessl.json that matches this request, then validate it.

  • Derive the correct five-field cron yourself; do not ask the user for a cron.
  • Give the schedule a stable lowercase kebab-case key.
  • The entry must be valid against the schedules block schema (the required fields are skill, cron, and environment).
  • Run tessl schedule validate from the repo root and make sure it passes.

Write a short note of what you did to result.md.

Output Specification

  • tessl.json: updated with a valid schedules block containing the new entry
  • result.md: a brief note with the schedule key, the cron you wrote, and the result of tessl schedule validate

Input Files

The 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" } } }

README.md

tile.json