
Cron Schedule
- 814 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
cron-schedule is an agent skill that creates persistent cron workers via CronCreate for developers who need recurring background agent tasks without external scheduler infrastructure.
About
cron-schedule is a ruvnet/ruflo skill that registers durable background workers using CronCreate with standard five-field cron expressions and prompt payloads. Workers survive session restarts and can dispatch hooks such as mcp__claude-flow__hooks_worker-dispatch for security audits, performance optimization, memory consolidation, and codebase mapping. The skill documents recommended intervals including */15 for audits, */30 for optimize and map workers, and hourly consolidate jobs. Developers reach for cron-schedule when agent workflows must run on a timer without standing up separate cron daemons or cloud schedulers. CronList and CronDelete support listing and removing registered workers.
- Generates valid cron expressions from natural language descriptions
- Validates and explains existing cron schedules
- Converts between cron formats and human-readable intervals
- Supports common scheduling patterns used in agent workflows
- Returns ready-to-use schedule objects for agent execution
Cron Schedule by the numbers
- 814 all-time installs (skills.sh)
- +5 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #331 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill cron-scheduleAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 814 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you schedule recurring agent cron jobs?
Let their AI agents reliably schedule recurring tasks, cron jobs, and timed operations without managing external schedulers.
Who is it for?
Developers running ruflo or claude-flow agents who need session-independent recurring workers for audits, optimization, or consolidation.
Skip if: One-shot timed tasks inside a single interactive session or teams already operating a dedicated external job scheduler they prefer to keep.
When should I use this skill?
A developer asks to schedule recurring agent work, set up cron workers, or run background audits on an interval.
What you get
Registered CronCreate workers with cron schedules, prompts, and surviving background dispatch entries manageable via CronList and CronDelete.
- registered cron worker definitions
- recurring agent dispatch schedules
Files
Use CronCreate for workers that must survive session restarts:
CronCreate({ schedule: "*/15 * * * *", prompt: "Run security audit worker via mcp__claude-flow__hooks_worker-dispatch" })
Recommended Schedules
| Worker | Cron | Description |
|---|---|---|
| audit | */15 * * * * | Security scanning |
| optimize | */30 * * * * | Performance optimization |
| consolidate | 0 * * * * | Memory consolidation |
| map | */30 * * * * | Codebase mapping |
| testgaps | */15 * * * * | Test coverage analysis |
| document | 0 */2 * * * | API documentation |
When to Use Cron vs Loop
- `/loop`: In-session, cache-aware, self-pacing. Use for active development.
- CronCreate: Persistent, survives restarts. Use for CI/monitoring.
Related skills
FAQ
Which API does cron-schedule use?
cron-schedule uses CronCreate to register workers with a cron schedule string and prompt, plus CronList and CronDelete for management. Example: CronCreate({ schedule: "*/15 * * * *", prompt: "Run security audit worker..." }).
Do cron-schedule workers survive session restarts?
cron-schedule workers created via CronCreate are persistent background workers designed to survive session restarts, unlike one-off in-session timers.