hermes-cron-jobs

Create, verify, and test Hermes cron jobs with pinned models and delivery targets.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill hermes-cron-jobs-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-cron-jobs
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/devops/hermes-cron-jobs
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill hermes-cron-jobs-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hermes cron jobs silently fail when the global inference config drifts from create-time settings, when attached skill names are wrong, or when the gateway is not running. This Skill encodes the reliability rules and full lifecycle workflow so scheduled autonomous jobs actually fire and deliver. ## Core Features & Use Cases - Pinned Job Creation: Create cron jobs via the CLI with explicit --model and --provider flags to prevent silent drift-skip failures. - Lifecycle Verification: Verify registration with hermes cron list, test immediately with hermes cron run, and inspect output files under <profile>/cron/output/. - Delivery & Gateway Checks: Discover Telegram or other delivery wiring from the profile .env, and surface gateway-not-running warnings before jobs silently never fire. - Use Case: A user asks for a daily AI digest delivered to Telegram at 2pm. The Skill writes a self-contained prompt file, creates a pinned job via CLI, tests it, and confirms the gateway is running. ## Quick Start Create a Hermes cron job that runs every day at 2pm and delivers a summary to Telegram, pinned to the current model and provider.

Frequently Asked Questions about hermes-cron-jobs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a scheduled cron job in Hermes Agent?▼

Use the CLI command `hermes cron create` with a cron schedule, prompt, name, and delivery target. Always pin the model and provider with `--model` and `--provider` flags, since the cronjob tool does not expose pinning and unpinned jobs get skipped on config drift.

Why is my Hermes cron job failing with a drift-skip error?▼

The job is unpinned and the global inference config changed since creation, so Hermes skips it to prevent unintended spend. Fix it by running `hermes cron edit <id> --model <id> --provider <provider>` to pin explicit values, then test with `hermes cron run <id>`.

Why does my Hermes cron job test successfully but never fire on schedule?▼

The gateway is not running, so no job fires automatically even though manual `hermes cron run` works. Start it with `hermes gateway install` for auto-start or `hermes gateway run` in the foreground, and check `hermes cron list` for the gateway warning.

How do I deliver Hermes cron job output to Telegram?▼

Set `TELEGRAM_BOT_TOKEN` and `TELEGRAM_HOME_CHANNEL` in the profile `.env`, then create the job with `--deliver telegram` to route to the home channel. Have the prompt emit exactly `[SILENT]` when there is nothing to report to suppress delivery.

What happens if I attach a nonexistent skill to a Hermes cron job?▼

The job still runs but injects a warning that the skill was not found, and that notice leaks into every delivered message. Verify skill names with `skills_list` or `skill_view` before attaching, and drop dead references rather than guessing.