right-cronlisted

# /right-cron -- Cron Job Manager ## When to Activate Activate this skill when: - The user mentions "cron", "cron jobs", "scheduled tasks", "reminders", or "Right Cron" - The user asks to schedule, create, remove, or change a recurring or one-shot task - The user asks to run something at a specific time or after a delay - The user asks about cron run history or why a job failed - **You (the agent) need to return to a task without a new user message** — e.g. retrying a transient upstream failure (502/timeout), polling a long-running external job, or honoring a "let me know when X" request. Cron is the only deferred-action mechanism available to you; if you'd otherwise say "I'll try again later", create a one-shot cron instead of promising it. ## How It Works Cron specs are stored in the agent database. The Rust runtime reconciles specs continuously and schedules jobs automatically. Use MCP tools to manage specs — no file creation needed. ## Creating a Cron Job **Minimum delivery latency.** A cron notification is held in the delivery queue until the chat has been idle for **{{ idle_threshold_min }} minutes** (UX-politeness gate — see "Triggering ≠ delivery" below). Therefore: - Never promise the user a reminder sooner than {{ idle_threshold_min }} minutes from now. The scheduled `run_at` can be sooner, but the user will not actually see the message until the chat has been quiet for {{ idle_threshold_min }} minutes. - If the user requests a reminder in les