Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ruvnet/ruflo --skill cron-schedule -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/cron-schedule/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cron-schedule/

From the same set104

The whole set →
ruflo ruvnet This skill adds multi-agent orchestration, memory, routing, and MCP tools to a project. Use it for swarm tasks and multi-step workflows. Claude Code CX Codex Cursor +1 4,000installs Swarm Orchestration ruvnet Skill for managing agent swarms with parallel execution, dynamic topology, and automatic load balancing. Use when a single agent is not enough and you need to orchestrate specialists of different types. Claude Code CX Codex Cursor +1 2,100installs github-project-management ruvnet Turns issue triage and board upkeep into gh and ruv-swarm calls: labels, subtasks, duplicate lookup. Useful when the tracker holds more tickets than order. Claude Code CX Codex Cursor +1 1,400installs github-workflow-automation ruvnet Automates GitHub Actions with AI agent coordination. Generates optimised pipelines, manages pull requests, analyzes failed runs, and deploys updates with risk assessment. Claude Code CX Codex Cursor +1 1,300installs github-code-review ruvnet Runs a swarm of specialized AI agents to inspect GitHub pull requests for security, performance, and architecture issues. Claude Code CX Codex Cursor +1 1,300installs stream-chain ruvnet Chains sequential agent steps together using streaming JSON flow and provides ready-to-run pipelines. Claude Code CX Codex Cursor +1 1,200installs flow-nexus-swarm ruvnet Deploy cloud-based AI agent swarms and define event-driven workflows with message queues. Use it to coordinate tasks, inspect runs, and scale a swarm. Claude Code CX Codex Cursor +1 1,200installs performance-analysis ruvnet Detects bottlenecks in Claude Flow swarms, profiles agent operations, and generates reports with actionable optimization recommendations. Claude Code CX Codex Cursor +1 1,200installs

Similar

autonomous-agents sickn33 A skill about building autonomous agents that stay reliable: ReAct and plan-execute loops, goal decomposition, reflection, and the math of compounding step failures. Claude Code CX Codex Cursor +1 1,200installs groups-and-containers phaserjs A Phaser 4 skill covering Group, Container and Layer, object pooling and nested transforms, so you stop guessing how to organise sprites. Claude Code CX Codex Cursor +1 790installs eval-harness-first Seth Hobson Builds the evaluation harness before fine-tuning with goldens, graders, judge calibration, and a base-model baseline. Useful for tracking regressions. Claude Code CX Codex Cursor 2,600installs react-email vercel-labs Turns JSON email specs into HTML or plain-text output with React Email. Use it for email catalogs, generated specs, and transactional message templates. Claude Code CX Codex Cursor +1 1,400installs nitro Anthony Fu A skill with Nitro v3 references: file-based routing, route rules, caching, storage and deployment presets. Use it when the agent edits nitro.config or writes H3 handlers. Claude Code CX Codex Cursor +1 2,600installs validate-skills Callstack Checks skills in skills/ against the agentskills.io specification and Claude Code practices. Use it when authoring or reviewing a skill collection. Claude Code CX Codex Cursor +1 7,200installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. Claude Code 711,230installs

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

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor