What problem does it solve? Cron jobs that fire at the wrong time, produce unreachable output files, or fail to deliver Discord DMs are hard to debug without deployment-specific knowledge. This Skill captures locally-verified facts about how the Hermes scheduler, manual runs, and DM delivery actually behave on this homeserver deployment. ## Core Features & Use Cases - Timezone Debugging: Explains that bare cron expressions evaluate in server local time (America/New_York), not UTC, and shows how to verify via the UTC offset on next_run_at from cronjob(action='list'). - Output Retrieval: Documents that cron transcript files on the Windows host are unreachable from the container, and that session_search on the cron_<job_id>_<timestamp> session is the working alternative. - Discord DM Delivery: Provides the verified pattern for DM delivery — deliver: local plus an explicit mcp__discordmessenger__discord_dm call made exactly once. - Use Case: A user reports a job "didn't fire at 7am." Load this Skill to check the offset suffix on next_run_at, discover the job was actually scheduled for 11am local time, and correct the cron expression without layering a bogus UTC conversion. ## Quick Start Ask the agent to check why a Hermes cronjob fired at the wrong time by listing the job and inspecting the timezone offset on its next_run_at timestamp.
