Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vexa-ai/scheduling
Set up recurring or scheduled work — anything the user wants run on a schedule, repeatedly, or at a future time ("every morning", "each weekday at 9am", "daily digest", "weekly report", "remind me", "run this on a cron"). Teaches how to author a durable Vexa Scheduler routine that survives restarts. Use this instead of any OS cron job, system timer, or session-only reminder.
Passed 20 of 21 test cases with the skill, and 7 of 21 without it.
and 14 more in the full report
14 fixed6 passed either way0 still failing1 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a routine scheduled every Friday at midnight to generate an end-of-week report titled 'End Of Week Status'. What exact path and filename should be created in the workspace?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies a file path under routines/ using a slug filename with .md extension. | Missed | Passed |
| Uses the 5-field cron expression 0 0 * * fri or 0 0 * * 5. | Passed | Passed |
The instructions your model reads when the skill loads.
When the user asks for ANYTHING that should run on a schedule or repeat over time (a daily digest, a weekly report, a periodic check, a future reminder), you create a routine file in this workspace. The agent-api reconciler compiles it into a durable Vexa Scheduler job that survives restarts and process death — it is the only correct mechanism for scheduled work here.
NEVER do any of these for scheduled work:
crontab, /etc/cron.*)sleep loopAll of those die on restart or when your turn ends. Only a routine file is durable.
Write one file at routines/<name>.md (<name> is a short slug; the filename
stem becomes the routine name). It is a normal governed workspace file — just write
it; you do not run git.
The file is YAML frontmatter plus an optional markdown body:
| field | required | meaning |
|---|---|---|
enabled | no (default true) | false cancels the job but keeps the file for later re-enable |
cron | yes (when enabled) | a standard 5-field cron expression (min hour dom mon dow) |
prompt | yes (when enabled) | the instruction sent to the agent on each run (non-empty) |
The optional markdown body below the second --- is appended to prompt as extra
context for each run.
Five fields, space-separated: minute hour day-of-month month day-of-week.
Day-of-week is 0–7 (0 and 7 are both Sunday); mon/tue/… and jan/feb/…
names are accepted, as are ranges (mon-fri), lists (1,15), and steps (*/15).
test cases passed, vs 7 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.