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.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 2816
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add Vexa-ai/vexaСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
scheduling — durable recurring work
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:
- create an OS cron job (
crontab,/etc/cron.*) - create a systemd timer or any other system timer
- start a shell background loop /
sleeploop - leave a "session-only" reminder (your turn ends and it is gone)
All of those die on restart or when your turn ends. Only a routine file is durable.
How to create a routine
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.
cron format
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).
Examples:
0 8 * * *— every day at 08:0030 9 * * mon-fri— 09:30 on weekdays0 17 * * fri— 17:00 every Friday0 * * * *— top of every hour
Worked example
For "every weekday at 9am, give me a digest of yesterday's meetings", create
routines/morning-digest.md:
---
enabled: true
cron: "30 9 * * mon-fri"
prompt: "Compile a short digest of yesterday's meetings and open tasks from kg/entities/, and summarize what needs attention today."
---
Keep it under ~10 bullet points. Group by person/company. Link entities with [[wikilinks]].