Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jshchnz avatar

Scheduler

  • 548 installs
  • 508 repo stars
  • Updated January 19, 2026
  • jshchnz/claude-code-scheduler

scheduler is a Claude skill that generates, validates, and explains five-field cron expressions for developers scheduling recurring agent tasks, jobs, or automations.

About

scheduler is a Claude Code skill with a complete cron expression reference for recurring job scheduling. It documents the standard five-field format—minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–6, Sunday=0)—plus special characters asterisk, comma lists, ranges, and step values. Examples include 0 9,17 * * * for 9:00 AM and 5:00 PM daily. Developers reach for scheduler when configuring Claude Code scheduled tasks, CI cron triggers, or any automation that needs a correct crontab string without misreading field order.

  • Complete cron expression syntax reference with field ranges and special characters
  • Detailed explanations of *, ,, -, / operators with real examples
  • Common time-based patterns including every X minutes, hourly, and daily schedules
  • Daily, weekly, and monthly scheduling patterns for production use
  • Visual breakdown table for quick lookup during agent scheduling

Scheduler by the numbers

  • 548 all-time installs (skills.sh)
  • +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #402 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jshchnz/claude-code-scheduler --skill scheduler

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs548
repo stars508
Security audit2 / 3 scanners passed
Last updatedJanuary 19, 2026
Repositoryjshchnz/claude-code-scheduler

How do you write a valid cron expression?

Generate, validate, and understand cron expressions for scheduling recurring agent tasks, jobs, or automations.

Who is it for?

Developers configuring recurring agent tasks, cron jobs, or scheduled automations who need correct five-field syntax.

Skip if: One-off delayed tasks better served by at-style schedulers or complex workflow orchestrators like Airflow DAGs.

When should I use this skill?

The user asks for a cron schedule, crontab syntax, recurring job timing, or help validating a cron expression.

What you get

Validated five-field cron strings with documented minute, hour, day, month, and weekday schedules.

  • validated cron expressions
  • cron syntax documentation

By the numbers

  • Standard five-field cron covers minute 0–59, hour 0–23, day 1–31, month 1–12, weekday 0–6
  • Example schedule 0 9,17 * * * defines two daily run times

Files

SKILL.mdMarkdownGitHub ↗

Scheduling Assistant

You help users set up and manage scheduled Claude Code tasks. You can:

  • Convert natural language to cron expressions ("every weekday at 9am" -> "0 9 1-5")
  • Explain cron syntax and scheduling concepts
  • Set up native OS schedulers (launchd, cron, Task Scheduler)
  • Troubleshoot scheduling issues
  • Suggest automation patterns for common workflows

Quick Start

To create a scheduled task:

/scheduler:schedule-add

To view all scheduled tasks:

/scheduler:schedule-list

One-Time vs Recurring Tasks

The scheduler supports both one-time and recurring tasks:

One-Time Tasks

For tasks that run once at a specific time:

  • "run at 3pm today"
  • "tomorrow at noon"
  • "next Tuesday at 2pm"

One-time tasks automatically clean up after execution.

Recurring Tasks

For tasks that repeat on a schedule:

  • "every day at 9am"
  • "daily at 6pm"
  • "weekdays at 10am"
  • Cron expressions like 0 9 * * 1-5

Detection rule: Unless "every", "daily", "weekly", or similar recurring keywords are present, the task is treated as one-time.

Git Worktree Mode (Isolated Branches)

For tasks that make changes, worktree mode runs them in isolation:

You: Every night at 2am, refactor deprecated API calls and push for review

Claude: Should this run in an isolated git worktree?
        → Yes, create branch and push changes
        → No, run in main working directory

You: Yes

Claude: ✓ Task created with worktree isolation
        Branch prefix: claude-task/
        Remote: origin

How it works: 1. Task triggers → creates fresh worktree with new branch 2. Claude runs in the worktree (isolated from main) 3. Changes are committed and pushed to remote 4. Worktree is cleaned up after successful push 5. You review the PR at your convenience

Configuration options:

OptionDefaultDescription
worktree.enabledfalseEnable worktree isolation
worktree.branchPrefix"claude-task/"Branch name prefix
worktree.remoteName"origin"Remote to push to

If push fails, the worktree is kept for manual review.

Cron Quick Reference

* * * * *
| | | | |
| | | | +-- Day of week (0-6, Sun=0)
| | | +---- Month (1-12)
| | +------ Day of month (1-31)
| +-------- Hour (0-23)
+---------- Minute (0-59)

Common patterns:

PatternDescription
0 9 * * *Daily at 9:00 AM
0 9 * * 1-5Weekdays at 9:00 AM
*/15 * * * *Every 15 minutes
0 */2 * * *Every 2 hours
0 9 1 * *First of month at 9:00 AM
0 9 * * 1Every Monday at 9:00 AM

For complete syntax, see CRON_REFERENCE.md.

Platform Setup

Tasks are executed by your OS's native scheduler:

  • macOS: launchd (LaunchAgents)
  • Linux: crontab
  • Windows: Task Scheduler

For platform-specific details, see PLATFORM_SETUP.md.

Common Use Cases

Daily Code Review

Schedule: 0 9 * * 1-5 (weekdays at 9am)
Command: /review-code --scope=yesterday

Weekly Dependency Audit

Schedule: 0 10 * * 1 (Mondays at 10am)
Command: Check for outdated dependencies and security vulnerabilities

Automated Testing

Schedule: 0 */4 * * * (every 4 hours)
Command: Run test suite and report failures

Troubleshooting

Task not running? 1. Check /scheduler:schedule-status for health 2. Verify task is enabled: /scheduler:schedule-list 3. Check logs: /scheduler:schedule-logs <task-id> 4. Ensure claude CLI is in PATH for scheduler

Common issues:

  • PATH not set correctly in scheduler environment
  • Working directory doesn't exist
  • Command syntax errors
  • Scheduler daemon not running

Helper Scripts

To validate a cron expression:

python scripts/parse-cron.py "0 9 * * 1-5"

Available Commands

CommandDescription
/scheduler:schedule-addCreate a new scheduled task
/scheduler:schedule-listView all scheduled tasks
/scheduler:schedule-remove <id>Remove a scheduled task
/scheduler:schedule-statusCheck scheduler health
/scheduler:schedule-run <id>Manually run a task
/scheduler:schedule-logs <id>View execution logs

Related skills

How it compares

Use scheduler for classic five-field cron strings when you do not need timezone-aware calendar DSLs from heavier orchestrators.

FAQ

What is the cron field order in scheduler?

scheduler uses the standard five-field order: minute (0–59), hour (0–23), day of month (1–31), month (1–12), then day of week (0–6 with Sunday=0).

How does scheduler express multiple run times?

scheduler shows comma lists in the hour field, such as 0 9,17 * * *, which runs at minute 0 of hours 9 and 17 every day.

Is Scheduler safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.