cron-scheduling

Create and manage one-shot and recurring cron jobs with timezone handling and delivery targets.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/decniner/HermesP1 --skill cron-scheduling-decniner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cron-scheduling
Source: https://github.com/decniner/HermesP1/tree/main/.hermes-backup/skills/productivity/cron-scheduling
Command: npx skills add https://github.com/decniner/HermesP1 --skill cron-scheduling-decniner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Scheduling reminders, recurring briefings, and automated tasks often fails due to timezone mistakes, unreachable delivery platforms, and misconfigured jobs. This Skill provides a reliable workflow for creating cron jobs that fire at the right time and deliver to the right place. ## Core Features & Use Cases - One-shot and recurring scheduling: Create jobs using ISO timestamps, durations (30m, 2h), natural language (every monday 9am), or standard cron expressions, with explicit timezone offsets to avoid UTC traps. - Delivery target management: Deliver job output to Telegram, Discord channels, or the current chat, with verification steps to confirm platforms and users are reachable before scheduling. - Script-based jobs (no_agent mode): Run Python or bash scripts on a schedule without LLM involvement, delivering stdout verbatim for zero-token automation like backups and inbox scans. - Use Case: Set up a daily 7 AM JST job that searches the web, curates content, and posts a formatted digest to a specific Discord channel, with a kanban task tracking its status. ## Quick Start Schedule a reminder for me tomorrow at 9 AM Japan time that sends a message to my Telegram chat.

Frequently Asked Questions about cron-scheduling

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

FAQPage Schema
How do I schedule a recurring cron job with an AI agent?▼

Use the cronjob tool with action='create' and a schedule in duration format (30m, 2h), natural language (every monday 9am), or a standard 5-field cron expression (0 9 * * *). Provide a prompt describing the task and optionally a delivery target.

How do I schedule a one-shot reminder at a specific time?▼

Pass an ISO timestamp with an explicit timezone offset, such as 2026-07-03T22:06:55+09:00, as the schedule. A bare timestamp without an offset is interpreted as UTC, which is a common source of mistimed jobs.

Why does my cron job fire at the wrong time?▼

The most common cause is a missing timezone offset, which makes the scheduler interpret the time as UTC. Always determine the user's timezone first, compute local time with Python or TZ-aware date commands, and include the offset in the ISO timestamp.

Can a cron job run a script without using an LLM?▼

Yes, set no_agent=True and provide a script filename relative to ~/.hermes/scripts/. The script's stdout is delivered verbatim, empty output stays silent, and no LLM tokens are consumed. Prompts and skills are ignored in this mode.

Why does sending a cron job result to a Telegram username fail?▼

Sending to telegram:@username fails with 'Chat not found' unless that user has messaged the bot at least once. Verify reachable targets with hermes send --list telegram, or use the numeric chat_id instead of a username.

What are the limitations of duration-based cron schedules?▼

Duration formats like 30m or 2h have a minimum granularity of one minute and do not support seconds. For sub-minute delays, use an ISO timestamp instead, and add a 5-10 second buffer so past timestamps are not silently skipped.