Scheduled Tasks (Cron)
المهام المجدولة Cron
Start with meaning, then move to detail.
This lesson explains Scheduled Tasks (Cron) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect What cron can do now, Creating scheduled tasks, In chat with /cron, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Scheduled Tasks (Cron) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
Schedule automated tasks with natural language, manage them with one cron tool, and attach one or more skills
What does the source say, and in what order?
- 01What cron can do now
Start here to understand the core idea or structure.
- 02Creating scheduled tasks
Read this after the foundation, then connect it to the previous step.
- 03In chat with /cron
Read this after the foundation, then connect it to the previous step.
- 04From the standalone CLI
Read this after the foundation, then connect it to the previous step.
- 05Through natural conversation
Read this after the foundation, then connect it to the previous step.
- 06Pre-dispatch configuration validation
Read this after the foundation, then connect it to the previous step.
- 07Letting unpinned jobs track global defaults
Read this after the foundation, then connect it to the previous step.
- 08Skill-backed cron jobs
Read this after the foundation, then connect it to the previous step.
- 09Single skill
Read this after the foundation, then connect it to the previous step.
- 10Multiple skills
Finish here to verify the result and special cases.
Copy only after you understand the effect.
/cron add 30m "Remind me to check the build"
/cron add "every 2h" "Check server status"
/cron add "every 1h" "Summarize new feed items" --skill blogwatcher
/cron add "every 1h" "Use both skills and combine the result" --skill blogwatcher --skill mapshermes cron create "every 2h" "Check server status"
hermes cron create "every 1h" "Summarize new feed items" --skill blogwatcher
hermes cron create "every 1h" "Use both skills and combine the result" \
--skill blogwatcher \
--skill maps \
--name "Skill combo"Every morning at 9am, check Hacker News for AI news and send me a summary on Telegram.Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.