cron
Schedule one-shot or recurring tasks — run a shell command or send a message to the agent on a timer.
Skill by daemon365
Chalk Labs
Need help deploying cron?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/daemon365-cron
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/cron
What's inside
- Skill name
cron- Description
- Schedule one-shot or recurring tasks — run a shell command or send a message to the agent on a timer.
- License
- MIT
- Instructions
- 108 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Cron
Use the `cron` tool to schedule tasks.
## Actions
| Action | Purpose |
|---|---|
| `add` | Create a new scheduled job |
| `list` | Show all jobs with next run time and last status |
| `remove` | Delete a job by `job_id` |
| `run` | Execute a job immediately regardless of schedule |
---
## Schedule kinds
| Goal | `schedule_kind` | Required fields |
|---|---|---|
| One-shot in N seconds from now | *(omit)* | `delay_seconds: N` |
| One-shot at exact time | `at` | `at_ms: <unix ms>` |
| Repeat every N seconds | `every` | `every_seconds: N` |
| Standard cron expression | `cron` | `cron_expr: "min hr dom mon dow"` |
**Rules:**
- For "in N minutes/hours" delays always use `delay_seconds` — never call `exec` or any tool to get the current timestamp; just pass the number of seconds to delay.
- Use `delete_after_run: true` for one-shot jobs that should automatically be removed after firing.
- For `schedule_kind=cron` use a standard 5-field expression (`min hour dom month dow`). An optional `tz` field sets the evaluation timezone (IANA name, e.g. `"Asia/Shanghai"`).
- Valid `schedule_kind` values: `at`, `every`, `cron`. Do **not** use `delay` or any other value.
---
## Payload kinds
| Goal | `payload_kind` | Required field |
|---|---|---|
| Run a shell command | `exec` | `command: "..."` |
| Inject a message into the agent | `agent_turn` | `message: "..."` |
**Rules:**
- `payload_kind` can be omitted: defaults to `exec` when `command` is set, otherwise `agent_turn`.
- Valid `payload_kind` values: `exec`, `agent_turn`. Do **not** use `message`, `agent_message`, or any other value.
- `message` is a **field name** for the text to inject, not a `payload_kind` value.
- For `agent_turn` jobs, the agent's reply is stored in the job's `lastOutput` field visible via `action=list`.
- An optional `session_id` scopes an `agent_turn` job to a specific conversation; omit it to use the default cron session.
---
## Examples
**One-shot in 10 minutes (exec):**
```
cron(action="add", name="ls home", delay_seconds=600,
command="ls ~", delete_after_run=true)
```
**Repeat every hour (exec):**
```
cron(action="add", name="disk check", schedule_kind="every", every_seconds=3600,
payload_kind="exec", command="df -h")
```
**Daily at 08:00 Shanghai time (agent_turn):**
```
cron(action="add", name="morning brief", schedule_kind="cron",
cron_expr="0 8 * * *", tz="Asia/Shanghai",
payload_kind="agent_turn",
message="Summarise my pending tasks and today's weather in Shanghai")
```
**Weekdays at 09:00 UTC (agent_turn):**
```
cron(action="add", name="standup", schedule_kind="cron",
cron_expr="0 9 * * 1-5",
payload_kind="agent_turn", message="Generate today's standup notes")
```
**List all jobs:**
```
cron(action="list")
```
**Remove a job:**
```
cron(action="remove", job_id="<id>")
```
**Run a job immediately:**
```
cron(action="run", job_id="<id>")
```
Ask agent "who are you" every 5 minutes and save reply to ~/reply.txt:
```
cron(action="add", name="who are you", schedule_kind="every", every_seconds=300,
payload_kind="agent_turn", message="who are you")
```
NOTE: the agent's reply is stored in `lastOutput` (see `action=list`).
To write it to a file directly, use an exec job instead:
```
cron(action="add", name="who to file", schedule_kind="every", every_seconds=300,
payload_kind="exec",
command="echo 'TODO: replace with actual bot CLI call' >> ~/reply.txt")
```From daemon365/bladebot, MIT.
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Mar 7, 2026 (7 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/daemon365/bladebot
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get cron running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
cron skill. Agent Mart. https://agentmart.dev/skills/daemon365-cron (last updated 2026-10-24)