Agent skill · operations · sickn33
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
Why this skill is useful
Provides specific scheduling patterns and commands for orchestrating AI agent runs that the AI would not reliably generate on its own.
What it needs
Requires hermes, pi installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Agent Self-Scheduling When to Use Use when the user asks for recurring, scheduled, heartbeat, or looped agent work. Use when you need to choose between cron, external schedulers, hooks, or built-in agent scheduling. Scheduling requires a direct user request; a guide or task-list entry is not permission to create background work. Preserve timezone, cadence, notification preferences and stop conditions; update an existing matching job instead of duplicating it. External messages and posting require explicit authorization. First inspect the actual host: prefer its supported scheduler/heartbeat when available (including Codex automations); otherwise use an explicitly authorized external clock. Host capabilities are not determined solely by the runtime name. Traditional five-field cron has one-minute granularity; other schedulers differ. Prefer event-driven checks and an appropriate cadence. Avoid tight LLM timers and indefinite loops. Camp A — one-shot agents, you own the clock These run once and exit (amnesiac unless resumed). Schedule them externally. Wrap in a clock: Gotchas (each breaks unattended runs if ignored): Permissions hang forever. Use the host's supported narrowly scoped permissions for the agreed task. Do not disable sandboxing or broadly auto-approve commands to avoid an unattended prompt; report unavailable required approval. Use JSON output (--output-format json / --json) so the wrapper parses results deterministically. Runs are amnesiac. Resume the exact recorded task/session ID or persist private scoped state. --last can select an unrelated task and is unsuitable for an unattended multi-project schedule. Pi has NO built-in scheduler/loop/heartbeat by design — external clock only (or a TS extension for agent-side timers). cmux — orchestration only, NO scheduler cmux has no timer/watch/cron. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/agent-self-scheduling