cron-scheduling — Claude Code skill: schedules and setup
The cron-scheduling skill covers recurring jobs with cron, node-cron, Spring @Scheduled, and APScheduler. Use it when a project needs timed or periodic execution.
MIT 162 installs ★ 50 updated 2026-10-23
npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a claude-codeWhat cron-scheduling does
The skill explains five-part cron syntax and applies it to node-cron, Spring @Scheduled, and APScheduler. Its examples cover calendar-based runs, fixed intervals, delays after completion, and explicit timezone settings.
It also covers distributed locks with Redlock and ShedLock, error handling, execution monitoring, logging, and graceful shutdown. A multi-instance deployment can run the same task more than once without a lock. Heavy queue work belongs in job-queues rather than inside a cron callback.
What it helps with
- write a cron expression for a recurring run
- schedule Node.js work with
node-cron - configure Java jobs with Spring
@Scheduled - run asynchronous Python tasks through APScheduler
- stop multiple instances from duplicating a scheduled job
Example prompts for the agent
- Create a cron expression that runs cleanup on weekdays at 9:00.
- Add a
node-crontask that syncs external data every 5 minutes. - Show how to guard an hourly report with Redlock across multiple instances.
How to install cron-scheduling
1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a claude-code2Manually: put the files in place
~/.claude/skills/cron-scheduling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cron-scheduling/
1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a codex2Manually: put the files in place
.agents/skills/cron-scheduling/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a cursor2Manually: put the files in place
.cursor/skills/cron-scheduling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install claude-dev-suite/claude-dev-suite skills/infrastructure/cron-scheduling2Manually: put the files in place
.github/skills/cron-scheduling/SKILL.md1Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a gemini-cli2Platform CLI
gemini skills install https://github.com/claude-dev-suite/claude-dev-suite --path skills/infrastructure/cron-schedulingManually: put the files in place
.devin/skills/cron-scheduling/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cron-scheduling
How do I install cron-scheduling in Claude Code?
Run npx skills add claude-dev-suite/claude-dev-suite --skill cron-scheduling -a claude-code. The skill file is placed at ~/.claude/skills/cron-scheduling/SKILL.md.
What does cron-scheduling do?
It helps create cron expressions and recurring jobs for node-cron, Spring @Scheduled, and APScheduler. It also covers locking patterns for scheduled work shared by multiple instances.
How can I prevent duplicate cron runs across instances?
Use a distributed lock such as Redlock in Node.js or ShedLock with Spring. Without one, separate instances can execute the same scheduled task at the same time.
Source text
SKILL.md · MIT
---
name: cron-scheduling
description: |
Cron and scheduled task management. node-cron, cron expressions, Spring
@Scheduled, APScheduler (Python), and distributed scheduling patterns.
USE WHEN: user mentions "cron", "scheduled task", "cron job", "node-cron",
"@Scheduled", "APScheduler", "periodic task", "crontab"
DO NOT USE FOR: job queues with workers - use `job-queues`;
one-off delayed tasks - use `job-queues`
allowed-tools: Read, Grep, Glob, Write, Edit
---
# Cron Scheduling
## Cron Expression Syntax
```
┌─────── minute (0-59)
│ ┌────── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌──── month (1-12)
│ │ │ │ ┌─── day of week (0-7, 0 and 7 = Sunday)
│ │ │ │ │
* * * * *
```
| Expression | Schedule |
|------------|----------|
| `0 * * * *` | Every hour |
| `*/15 * * * *` | Every 15 minutes |
| `0 9 * * 1-5` | Weekdays at 9:00 AM |
| `0 0 1 * *` | First day of month, midnight |
| `0 */6 * * *` | Every 6 hours |
## Node.js (node-cron)
```typescript
import cron from 'node-cron';
// Run every day at 2:00 AM
cron.schedule('0 2 * * *', async () => {
console.log('Running daily cleanup...');
await cleanupExpiredSessions();
}, {
timezone: 'America/New_York',
});
// Run every 5 minutes
cron.schedule('*/5 * * * *', async () => {
await syncExternalData();
});
```
### With Distributed Locking (prevent duplicate runs)
```typescript
import { Redlock } from 'redlock';
const redlock = new Redlock([redis]);
cron.schedule('0 * * * *', async () => {
let lock;
try {
lock = await redlock.acquire(['cron:hourly-report'], 60000);
await generateHourlyReport();
} catch (err) {
if (err instanceof Redlock.LockError) return; // Another instance has the lock
throw err;
} finally {
await lock?.release();
}
});
```
## Spring @Scheduled (Java)
```java
@Component
@EnableScheduling
public class ScheduledTasks {
@Scheduled(cron = "0 0 2 * * *") // Daily at 2 AM
public void dailyCleanup() {
sessionRepo.deleteExpired();
}
@Scheduled(fixedRate = 300000) // Every 5 minutes
public void syncData() {
externalService.sync();
}
@Scheduled(fixedDelay = 60000) // 60s after last completion
public void processQueue() {
queueService.processNext();
}
}
```
### Distributed Scheduling (ShedLock)
```java
@Scheduled(cron = "0 */10 * * * *")
@SchedulerLock(name = "syncInventory", lockAtLeastFor = "5m", lockAtMostFor = "10m")
public void syncInventory() {
inventoryService.syncAll();
}
```
## Python (APScheduler)
```python
from apscheduler.schedulers.asyncio import AsyncIOScheduler
from apscheduler.triggers.cron import CronTrigger
scheduler = AsyncIOScheduler()
@scheduler.scheduled_job(CronTrigger(hour=2, minute=0))
async def daily_cleanup():
await cleanup_expired_sessions()
@scheduler.scheduled_job('interval', minutes=5)
async def sync_data():
await sync_external_data()
scheduler.start()
```
## Anti-Patterns
| Anti-Pattern | Fix |
|--------------|-----|
| Cron on multiple instances without locking | Use distributed lock (Redlock, ShedLock) |
| Long-running cron blocks next run | Use job queue for heavy work |
| No error handling in cron | Wrap in try-catch, log errors, alert |
| Hardcoded schedule | Use environment variable or config |
| No monitoring of cron execution | Log start/end times, track failures |
## Production Checklist
- [ ] Distributed locking for multi-instance deployments
- [ ] Error handling with alerting
- [ ] Execution time monitoring
- [ ] Timezone explicitly set
- [ ] Graceful shutdown (finish current job)
- [ ] Cron expressions documented
© claude-dev-suite · MIT · claude-dev-suite/claude-dev-suite