Create, audit, and troubleshoot scheduled cron jobs in Hermes Agent.
npx skills add https://github.com/tapway/shogun-os --skill hermes-cron-jobs-tapway
Please help me install this Agent Skill. Skill: hermes-cron-jobs Source: https://github.com/tapway/shogun-os/tree/main/skills/hermes/hermes-cron-jobs Command: npx skills add https://github.com/tapway/shogun-os --skill hermes-cron-jobs-tapway
--model flags, and script path rules — that cause silent failures, and diagnosing broken jobs requires knowing where output files and delivery origins actually live. ## Core Features & Use Cases - Correct Job Creation: Enforces the critical argument ordering (prompt immediately after schedule) and explains --script, --skill, --deliver, and agent vs no-agent modes. - Failure Diagnosis: Walks through reading timestamped .md output files, grouping errors by root cause (auth expiry, lock contention, timeouts, daemon-in-cron), and fixing causes instead of individual jobs. - Delivery Auditing & Migration: Shows how to read jobs.json origin fields to audit which chats receive job output and how to move jobs between Hermes profiles. - Use Case: When three cron jobs all fail with the same Google OAuth error, use this Skill to trace the .md output logs, identify the shared root cause, and fix the auth once instead of patching three scripts. ## Quick Start Ask the agent to create a weekday 9am cron job that runs a script and delivers results back to the originating chat.High-intent search queries and answers about installing and using this skill.
Run `hermes cron create` with the schedule first, then the prompt as a positional argument immediately after, followed by named flags like `--name`, `--skill`, and `--deliver`. Placing the prompt after named flags fails with an unrecognized arguments error.
The error occurs when the prompt string appears after named flags instead of immediately after the schedule. The prompt is a positional argument, and flags like `--model` or `--prompt` do not exist on the create command.
Read `~/.hermes/cron/jobs.json` and search for the target `chat_name` in each job's `origin` object. Jobs with `deliver: origin` send output to that chat, while `deliver: local` jobs run silently.
Output is stored as timestamped Markdown files at `~/.hermes/cron/output/<job_id>/<timestamp>.md`, not as stdout or stderr log files. Read the most recent `.md` file to see script output or agent errors.
No-agent scripts have a 120-second hard timeout from the cron scheduler. Common causes include importing accumulated directories, daemon loops that never exit, or hanging API calls from expired auth tokens.
No, the CLI does not support a `--model` flag. Use the programmatic cronjob tool instead, which accepts a `model` parameter on create and supports model pinning via its update action.
diazMelgarejoConfigures and validates Hermes and ECC partner CLI wiring on Windows.
Kastalien-ResearchSchedule cron-style tasks that trigger agent interactions and deliver messages.
huidgeDiagnose cron job failures by analyzing status, logs, and gateway errors.
L3DigitalNetManage cron daemon and crontab administration for Linux job scheduling.