hermit-routines

Routines

Register and manage scheduled routines. Where the Monitor tool is available, all enabled routines except heartbeat-restart run from ONE persistent Monitor subprocess that decides eligibility outside the session — a skipped fire costs zero model tokens. heartbeat-restart stays a CronCreate re-arm anchor: its skill IS load, so its daily fire re-arms the monitor and the anchor CronCreate — and, unless heartbeat.enabled is explicitly false, restores the heartbeat monitor too. The watchdog re-arms a monitor whose liveness has gone stale as a second net, on a resting session too. Where Monitor is unavailable (Bedrock/Google Cloud Agent Platform/Foundry, DISABLE_TELEMETRY/CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC), load falls back to per-routine CronCreates.

Usage

/claude-code-hermit:hermit-routines load              register/reconcile: monitor mode if available, else CronCreate diff-register
/claude-code-hermit:hermit-routines load --reset      unconditional reset: tear down + recreate everything
/claude-code-hermit:hermit-routines run <ids>          [internal] ROUTINE_DUE handler — invoked by the monitor's notification
/claude-code-hermit:hermit-routines list               list configured routines from config.json
/claude-code-hermit:hermit-routines status              show monitor/anchor state (or CronCreate registrations in fallback mode)
/claude-code-hermit:hermit-routines stop [id]           stop the monitor (or a specific fallback-mode CronCreate)
/claude-code-hermit:hermit-routines stop --all          stop everything

list, status, stop and the notes live in reference.md, beside this file in the skill's Base directory — Read it for those. load and run stay here: every always-on launch pays for them.

Plan

load

Called automatically by hermit-start.ts on always-on launches. Can also be called manually to apply config changes mid-session.

1. Resolve the plugin root path: derive it from this skill's Base directory, which the harness injects into the invocation context as <plugin_root>/skills/hermit-routines. Strip the trailing /skills/hermit-routines to get pluginRoot. This works in both installed and --plugin-dir modes. ($CLAUDE_PLUGIN_ROOT is NOT a Bash env var at runtime — evaluating it in Bash always returns empty. The braced ${CLAUDE_PLUGIN_ROOT} form is text-substituted in skill markdown only in installed mode. Neither is reliable here — always use the Base-directory derivation.) The resolved pluginRoot must be baked into the Monitor command and into any CronCreate-delivered prompt at registration — it is not available inside either subprocess or cron-delivered prompts.