cron-schedule — Claude Code skill: what it does, how to install
Schedules background worker runs via CronCreate during an active session. Useful for recurring security audits, test gap reviews, and codebase mapping.
npx skills add ruvnet/ruflo --skill cron-schedule -a claude-codeWhat cron-schedule does
This skill configures recurring background workers directly inside a Claude Code session with CronCreate. Each job accepts a standard five-field cron expression, a prompt, and a recurring boolean flag. Note that a schedule: parameter does not exist. Workers trigger routines via mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch, such as running the audit scan every 15 minutes or checking testgaps.
All scheduled tasks are tied directly to your active session. They stop immediately when the session ends, and recurring jobs expire automatically after 7 days. You can inspect running jobs with CronList and cancel them using CronDelete. If you need tasks to persist after closing the terminal, this tool will fall short; use /schedule or an OS-level scheduler calling npx @claude-flow/cli@latest hooks worker dispatch --trigger audit instead.
What it helps with
- run scheduled security audits inside an active terminal session
- trigger codebase mapping routines every 30 minutes
- schedule test coverage reviews with the testgaps worker
- consolidate session memory at regular intervals
Example prompts for the agent
- Schedule the audit worker with cron-schedule using interval */15 * * * *
- Run the optimize worker every 30 minutes via CronCreate
- Check active session jobs with CronList and delete worker <id>
How to install cron-schedule
1Skills CLI (Vercel)
npx skills add ruvnet/ruflo --skill cron-schedule -a claude-code2Manually: put the files in place
~/.claude/skills/cron-schedule/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cron-schedule/
1Skills CLI (Vercel)
npx skills add ruvnet/ruflo --skill cron-schedule -a codex2Manually: put the files in place
.agents/skills/cron-schedule/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ruvnet/ruflo --skill cron-schedule -a cursor2Manually: put the files in place
.cursor/skills/cron-schedule/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ruvnet/ruflo cron-schedule2Manually: put the files in place
.github/skills/cron-schedule/SKILL.md1Skills CLI (Vercel)
npx skills add ruvnet/ruflo --skill cron-schedule -a gemini-cli2Platform CLI
gemini skills install https://github.com/ruvnet/ruflo --path plugins/ruflo-loop-workers/skills/cron-scheduleManually: put the files in place
.devin/skills/cron-schedule/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ruvnet/ruflo --skill cron-schedule -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set104
The whole set →Similar
Questions about cron-schedule
How to install cron-schedule in Claude Code?
Run npx skills add ruvnet/ruflo --skill cron-schedule -a claude-code in your terminal. You can also place it manually at ~/.claude/skills/cron-schedule/SKILL.md.
What does cron-schedule do?
It schedules in-session background workers using the CronCreate tool with a five-field cron syntax. Workers run tasks like security checks or documentation updates on a timer.
Do scheduled workers survive after the session closes?
No, jobs stop when you close the session and auto-expire after 7 days. For persistent monitoring outside the session, use /schedule or an OS scheduler like cron or systemd.
Source text
SKILL.md · MIT
---
name: cron-schedule
description: Schedule persistent background workers via CronCreate
argument-hint: "<worker-name> [--interval CRON]"
allowed-tools: CronCreate CronList CronDelete mcp__plugin_ruflo-core_ruflo__hooks_worker-dispatch
---
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
| 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, 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.
© ruvnet · MIT · ruvnet/ruflo