Skills Productivity Cron Worker Scheduling

Cron Worker Scheduling

v20261020
cron-schedule
Schedule persistent in-session background workers using CronCreate with five-field cron expressions. Run security audits, optimization, memory consolidation, and codebase mapping on fixed clocks, with optional OS schedulers for jobs that outlive the session.
Get Skill
473 downloads
Overview

Use CronCreate for a worker that should fire on a clock while this Claude Code session is open:

CronCreate({ cron: "*/15 * * * *", prompt: "Dispatch the audit worker with mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch({ trigger: \"audit\" }) and report anything critical", recurring: true })

The parameters are cron (five-field expression), prompt and recurring. A schedule: field does not exist. These jobs live in the session: they stop when you close it, and recurring jobs expire on their own after 7 days. Cancel one sooner with CronDelete (find its id with CronList). For a worker that must keep running after the session ends, use /schedule (cloud routines) or an OS scheduler (cron, systemd timer) that calls npx @claude-flow/cli@latest hooks worker dispatch --trigger audit.

Recommended Schedules

WorkerCronDescription
audit*/15 * * * *Security scanning
optimize*/30 * * * *Performance optimization
consolidate0 * * * *Memory consolidation
map*/30 * * * *Codebase mapping
testgaps*/15 * * * *Test coverage analysis
document0 */2 * * *API documentation

When to Use Cron vs Loop

  • /loop: In-session, self-pacing. Use for active development.
  • CronCreate: In-session, fixed clock, auto-expires after 7 days. Use for regular checks while you work.
  • /schedule or an OS scheduler: Survives the session. Use for CI-style monitoring.
Info
Category Productivity
Name cron-schedule
Version v20261020
Size 1.71KB
Updated At 2026-10-21
Language