holix-cron

## When to use this skill The user wants a **recurring or scheduled task** (daily report, hourly check, weekly backup summary, etc.). **Always use Holix built-in cron** — jobs stored in the profile and executed by the gateway scheduler with the same agent stack as chat. ## Do NOT - Do **not** create or edit system `crontab`, `launchd` plists, or `systemd` timers for Holix agent work. - Do **not** write standalone Python/bash “scheduler” scripts that loop with `sleep` unless the user explicitly needs OS-level scheduling outside Holix. - Do **not** suggest third-party job runners when `holix gateway` can run the task. ## Prerequisites 1. **Gateway must be running** (scheduler lives inside gateway): - `holix gateway start` (background) or `holix gateway start -f` (foreground) - `holix gateway status` — verify running 2. Jobs are **per profile** (`--profile` / `HOLIX_PROFILE`). ## Storage (read-only for debugging) - Jobs: `~/.holix/profiles/<profile>/data/cron/jobs.json` - Run log: `~/.holix/profiles/<profile>/data/cron/runs.log` Prefer **commands** below; edit JSON only if the user insists. ## How to create a job Tell the user the slash command (TUI / Telegram) or run CLI yourself if you have shell access. **Slash (chat):** ``` /cron add <schedule> :: <task description> ``` Examples: - `/cron add every day at 9 :: Summarize yesterday's git activity` - `/cron add every 30 minutes :: Check disk space and alert if >90%` - `/cron add 0 9 * * 1-5 :: Morning stand...