scheduler

jshchnz/claude-code-scheduler · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jshchnz/claude-code-scheduler --skill scheduler
0 commentsdiscussion
summary

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

skill.md

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:

Option Default Description
worktree.enabled false Enable 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:

Pattern Description
0 9 * * * Daily at 9:00 AM
0 9 * * 1-5 Weekdays 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 * * 1 Every 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

Command Description
/scheduler:schedule-add Create a new scheduled task
/scheduler:schedule-list View all scheduled tasks
/scheduler:schedule-remove <id> Remove a scheduled task
/scheduler:schedule-status Check scheduler health
/scheduler:schedule-run <id> Manually run a task
/scheduler:schedule-logs <id> View execution logs
how to use scheduler

How to use scheduler on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add scheduler
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jshchnz/claude-code-scheduler --skill scheduler

The skills CLI fetches scheduler from GitHub repository jshchnz/claude-code-scheduler and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/scheduler

Reload or restart Cursor to activate scheduler. Access the skill through slash commands (e.g., /scheduler) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.851 reviews
  • Ganesh Mohane· Dec 20, 2024

    scheduler reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Carlos Singh· Dec 20, 2024

    scheduler reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Daniel Mehta· Dec 16, 2024

    Registry listing for scheduler matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Carlos Verma· Dec 16, 2024

    scheduler fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Kiara Thompson· Dec 4, 2024

    scheduler has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kiara Torres· Nov 27, 2024

    scheduler fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Isabella Patel· Nov 23, 2024

    Keeps context tight: scheduler is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Harper Abbas· Nov 19, 2024

    We added scheduler from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sakshi Patil· Nov 11, 2024

    I recommend scheduler for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Daniel Lopez· Nov 11, 2024

    I recommend scheduler for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 51

1 / 6