Menu
Schedule recurring agent tasks via Holix built-in gateway cron (not crontab or custom scripts)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement an SDD change from tasks.md — always ask self vs subagents first, then execute only after apply mode is set
Create Spec-Driven Development changes (OpenSpec-style) — multi-project openspec, understanding gate, assigned tasks before coding
Archive a completed SDD change — merge delta specs into main openspec/specs and move change to archive
Run frontend (and FE+BE) apps in Holix Studio: always bind 0.0.0.0, always open Studio preview links in chat, always prefer docker-compose with an nginx reverse proxy that joins frontend and backend. Use when starting Vite/Next/Nuxt/React, SPA+API monorepos, or any web app the user should open in Studio Browser. Invoke via /holix-studio-frontend-backend.
Author and manage Holix agent drop-in extensions so the agent can extend itself without editing Holix core. Use when the user asks to write an extension, add tools, register slash commands, list extensions, disable a broken extension, or self-modify agent capabilities. Invoke via /holix-extensions.
Full Holix sub-agent lifecycle: spawn, monitor, collect results, answer ask_user questions, approve tool confirmations, and delegate to external CLIs (holix launch). Use when the user asks about subagents, /subagent-spawn, delegate_to_subagent, background workers, sub-agent questions, /subagent-reply, holix launch + coder, or running tasks without blocking the main chat. Invoke via /holix-subagents.
| name | holix-cron |
| description | Schedule recurring agent tasks via Holix built-in gateway cron (not crontab or custom scripts) |
| tags | ["cron","schedule","holix","gateway","periodic","automation"] |
| user-invocable | true |
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.
crontab, launchd plists, or systemd timers for Holix agent work.sleep unless the user explicitly needs OS-level scheduling outside Holix.holix gateway can run the task.holix gateway start (background) or holix gateway start -f (foreground)holix gateway status — verify running--profile / HOLIX_PROFILE).~/.holix/profiles/<profile>/data/cron/jobs.json~/.holix/profiles/<profile>/data/cron/runs.logPrefer commands below; edit JSON only if the user insists.
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 standup prep from open issues/cron add hourly :: Quick health check of gatewayCLI (terminal):
holix cron add "every day at 9 :: Summarize logs"
holix cron list
holix cron disable <job-id>
holix cron enable <job-id>
holix cron remove <job-id>
every day at 9:00, every 30 minutes, hourly, daily, weekly, weekdays, every 2 hours0 9 * * *, */15 * * * *Task text after :: is the agent prompt for each run (be specific: what to check, output format, workspace assumptions).
| Action | Slash | CLI |
|---|---|---|
| List / UI | /cron or /cron list | holix cron list |
| Enable | /cron enable <id> | holix cron enable <id> |
| Disable | /cron disable <id> | holix cron disable <id> |
| Delete | /cron remove <id> | holix cron remove <id> |
Job IDs are short strings shown in the list (prefix match works).
TUI opens a modal with enable/disable/delete. Telegram has inline buttons under /cron.
cron-<job-id> (separate from the user's chat session).last_run_at, last_status (success / error / running), next_run_at, run_count.Holix automatically creates a cron job when the user writes a recurring request in natural language (Telegram, MAX, TUI), for example:
No /cron add needed for clear schedule + task phrasing. The host replies with job id and next_run_at. Gateway must still be running for execution.
You can also call the schedule_cron tool (schedule + task) when auto-detection did not fire.
schedule_cron tool or let the host auto-create; otherwise /cron add … or holix cron add "…".holix gateway start./cron list to verify next_run_at.If the user says “every Monday at 10 run X”, translate to:
/cron add every week :: X
(or 0 10 * * 1 :: X if they prefer explicit cron).
| Problem | Check |
|---|---|
| Job never runs | holix gateway status; gateway must be up |
| Invalid schedule | Use every day at 9 or valid 5-field cron |
| Task runs but fails | Read runs.log; fix prompt or model/profile config |
| Duplicate jobs | /cron list; remove old rule with /cron remove |
/init — one-shot project analysis, not periodicholix hub — skills/plugins, not scheduling