菜单
Schedule recurring agent tasks with the cronjob tool. Use when the user wants something to run on a schedule, when you finish a task that should recur, or when planning daily/weekly automations.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill automation-cron命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | automation-cron |
| description | Schedule recurring agent tasks with the cronjob tool. Use when the user wants something to run on a schedule, when you finish a task that should recur, or when planning daily/weekly automations. |
| version | 1.0.0 |
| author | Kevin Liu |
| license | MIT |
| metadata | {"agent-machines":{"tags":["cron","automation","scheduling","recurring"]}} |
I can schedule recurring tasks via the cronjob tool. They run as fresh agent sessions on the gateway scheduler, with results delivered back to the originating chat or to configured platforms.
Hermes accepts both natural language and crontab syntax:
"every 1h"
"every 30m"
"every 2h"
"every 1d at 09:00"
"daily at 04:00"
"every monday at 09:00"
"0 9 * * *" # crontab -- daily at 09:00 UTC
"30 */4 * * *" # crontab -- every 4 hours at :30
Three surfaces, same effect:
agent-machines cron create --skill blogwatcher --name
/cron add
cronjob(
action=,
schedule=,
prompt=,
name=,
skills=[],
)
A cron job can preload one or more skills before running its prompt. Skills are loaded in order; the prompt becomes the task instruction layered on top.
Use this when the job needs a recurring procedure (e.g. blogwatcher checks feeds, llm-wiki updates a knowledge base).
By default cron jobs run detached from any repo. Pass workdir to load AGENTS.md / CLAUDE.md and run terminal/file tools rooted in that directory:
cronjob(
action="create",
schedule="every 1d at 09:00",
workdir="/home/machine/projects/dedalus-monorepo",
prompt="Audit open PRs, summarize CI health, and post to #eng",
)
The path must be absolute and exist; relative paths are rejected.
cronjob action=list # show all jobs
cronjob action=pause id=... # pause a job
cronjob action=resume id=... # resume a job
cronjob action=run id=... # trigger immediately
cronjob action=remove id=... # delete a job
cronjob action=update id=... # edit schedule, prompt, skills, or workdir
Cron-run sessions cannot themselves create more cron jobs. Hermes disables cronjob inside cron executions to prevent runaway scheduling loops. If you want a job to spawn other jobs, do it via direct tool calls in chat instead.
These ship with the deployment and run automatically:
~/Documents/GitHub/my-wiki and post to chat.If the user describes a task that would benefit from recurrence ("every morning, check X"), I propose a cron with the exact cronjob action=create call before scheduling, so they can approve the schedule and prompt. Never add a cron silently.