Schedules recurring tasks and reminders for your agent.
Install
mkdir -p .claude/skills/cron && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1536" && unzip -o skill.zip -d .claude/skills/cron && rm skill.zipInstalls to .claude/skills/cron
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Schedule reminders and recurring tasks.Key capabilities
- →Schedule recurring tasks
- →Set one-time reminders
- →Execute dynamic tasks at intervals
- →List and remove scheduled jobs
How it works
The tool registers jobs with specified time expressions or intervals, triggering the agent to perform actions or send messages back to the originating session.
Inputs & outputs
When to use cron
- →Set daily reminders
- →Schedule periodic status checks
- →Trigger tasks at specific times
About this skill
Cron
Use the cron tool to schedule reminders or recurring tasks. New tasks run in the current chat. nanobot sends the agent's final reply to that chat. The user can change the task's chat in WebUI.
Write what to do in message. For a normal reminder or report, do not copy the current channel, chat ID, or instructions to call the message tool into the task. For example, use "Remind me to drink water", not "Call message to send to this chat".
If the user asks to send to other chats, preserve those recipients in the task instructions. Use the message tool for those sends and for file attachments. Existing tasks that explicitly request a message call still use it; changing the task's chat does not change explicit recipients in its instructions.
Choose by timing and notification behavior, not repetition. A specified time or interval uses cron, even when it repeats: "every day at 8am, remind me to drink water" is a cron task. Use HEARTBEAT.md for background checks with flexible timing that should notify only on actionable changes. Heartbeat does not guarantee a requested time or interval; do not substitute it for an explicit schedule.
Task Types
- Reminder - the agent replies with the reminder when the task runs
- Task - the agent follows the instructions and replies with the result
- One-time - runs once at a specific time, then auto-deletes
Examples
Fixed reminder:
cron(action="add", message="Time to take a break!", every_seconds=1200)
Dynamic task (agent executes each time):
cron(action="add", message="Check HKUDS/nanobot GitHub stars and report", every_seconds=600)
One-time scheduled task (compute ISO datetime from current time):
cron(action="add", message="Remind me about the meeting", at="<ISO datetime>")
Timezone-aware cron:
cron(action="add", message="Morning standup", cron_expr="0 9 * * 1-5", tz="America/Vancouver")
List/remove:
cron(action="list")
cron(action="remove", job_id="abc123")
Pause and resume an existing task without deleting its schedule or run history:
cron(action="disable", job_id="abc123")
cron(action="list", include_disabled=True)
cron(action="enable", job_id="abc123")
Disabling a task stops future runs; it does not cancel a running task or recall a queued reply. System-managed jobs such as heartbeat and Dream are protected; change their configuration instead.
Time Expressions
| User says | Parameters |
|---|---|
| every 20 minutes | every_seconds: 1200 |
| every hour | every_seconds: 3600 |
| every day at 8am | cron_expr: "0 8 * * *" |
| weekdays at 5pm | cron_expr: "0 17 * * 1-5" |
| 9am Vancouver time daily | cron_expr: "0 9 * * *", tz: "America/Vancouver" |
| at a specific time | at: ISO datetime string (compute from current time) |
Timezone
Use tz with cron_expr to schedule in a specific IANA timezone. New tasks use the runtime default timezone when tz is omitted. Updates retain the task's existing cron timezone.
Update a Task
Use cron(action="update", job_id="...", cron_expr="0 10 * * *") to change an existing task. Supply only the fields to change: name, message, or exactly one of every_seconds, cron_expr, and at. Omitted fields keep their values; empty names and instructions are rejected. A cron edit retains the existing timezone unless tz is supplied with cron_expr. Naive at values use the runtime default timezone.
Updates preserve the task ID, linked chat, history, enabled state, and automatic-deletion setting. Changing only the name or instruction does not move the next run. System-managed tasks cannot be edited.
Run History
Use cron(action="history", job_id="...", limit=5) to inspect recent executions, newest first. Each entry includes its time, status, duration in milliseconds, and any error. job_id is required; limit defaults to 5 and accepts 1–20. Listing jobs still shows only the last run.
History can be inspected for disabled jobs too. The scheduler retains at most 20 runs per job; deleted jobs, including automatically deleted one-time tasks, cannot be queried. This reads execution records, not task output or delivery receipts.
When not to use it
- →For periodic background checks that require no output
- →For tasks requiring high-frequency sub-second execution
Prerequisites
Limitations
- →Server local time used if no timezone specified
- →Not for silent background monitoring
How it compares
It allows for agent-executed tasks rather than simple notification-only scheduling.
Compared to similar skills
cron side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| cron (this skill) | 8 | 9mo | No flags | Beginner |
| zapier-workflows | 11 | 12mo | Review | Beginner |
| automation-brainstorm | 7 | 1y | No flags | Beginner |
| connect-apps | 6 | 10mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
automation-brainstorm
MacroMan5
Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.
connect-apps
ComposioHQ
Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
agent-workflow
ruvnet
Agent skill for workflow - invoke with $agent-workflow
workflow-automation
ruvnet
Workflow creation, execution, and template management. Automates complex multi-step processes with agent coordination. Use when: automating processes, creating reusable workflows, orchestrating multi-step tasks. Skip when: simple single-step tasks, ad-hoc operations.
zapier-make-patterns
davila7
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power