npx skills add ruvnet/ruflo --skill cron-schedule --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Use `CronCreate` for workers that must survive session restarts: `CronCreate({ schedule: "*/15 * * * *", prompt: "Run security audit worker via mcp__plugin_ruflo-core_ruflo__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.
- Recommended Schedules
- When to Use Cron vs Loop
What does the cron-schedule skill do?
Schedule persistent background workers via CronCreate
How do I install it?
Run `npx skills add ruvnet/ruflo --skill cron-schedule --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.