skills.rest
ruvnet
ruvnetCOMMUNITY
Explore all skills by this author →
Website𝕏@ruvGitHub

cron-schedule

Schedules persistent background workers using CronCreate cron expressions.

70.1k|8.4k|Updated Jun 2, 2025
Search Tags:#persistence#scheduling#Automation#ci#CRON#background workers#Monitoring
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill cron-schedule
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cron-schedule
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-loop-workers/skills/cron-schedule
Command: npx skills add https://github.com/ruvnet/claude-flow --skill cron-schedule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Background workers that need to run on a recurring basis disappear when a session ends, forcing users to manually restart monitoring, auditing, and maintenance tasks. This Skill schedules workers via CronCreate so they survive session restarts.

Core Features & Use Cases

  • Persistent Scheduling: Creates cron-based schedules for workers that continue running across session restarts, unlike in-session loops.
  • Recommended Presets: Provides ready-made cron expressions for common workers such as security audits (*/15 * * * ), performance optimization (/30 * * * *), memory consolidation (hourly), codebase mapping, test coverage analysis, and API documentation.
  • Use Case: A team wants automated security scanning every 15 minutes without keeping an interactive session open. Use this Skill to register a cron job that dispatches the audit worker on schedule.

Quick Start

Ask the assistant to schedule the audit worker to run every 15 minutes using a persistent cron schedule.

Frequently Asked Questions about cron-schedule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule a background worker with a cron expression?▼

Call CronCreate with a cron schedule and a prompt that dispatches the worker, for example CronCreate with schedule "*/15 * * * *" and a prompt invoking the worker-dispatch hook. The job then runs on that interval persistently.

When should I use CronCreate instead of the /loop command?▼

Use /loop for in-session, cache-aware, self-pacing work during active development. Use CronCreate when the worker must persist across session restarts, such as CI monitoring or recurring maintenance tasks.

What cron schedules are recommended for common workers?▼

Audit and testgaps workers run every 15 minutes, optimize and map every 30 minutes, consolidate hourly, and document every 2 hours. These presets balance freshness against resource usage.

How do I list or delete scheduled cron jobs?▼

Use CronList to view all registered cron jobs and CronDelete to remove one. These tools manage the persistent schedules created by CronCreate.

Do cron-scheduled workers keep running after my session ends?▼

Yes. Workers registered through CronCreate are persistent and survive session restarts, which is the key difference from the in-session /loop approach.

Related Skills

Explore More Software Engineering Skills→
clonable-edenclonable-eden
15

cron

Manage recurring tasks via launchd and crontab with cron expressions.

Community
Intermediate
All-The-VibesAll-The-Vibes
50

triage

Triage findings into ready-to-work todos with YAML frontmatter updates.

Official
Intermediate
epologeeepologee
3

recap

Summarize session context, git state, and background tasks into three sections.

Community
Intermediate
youssefKadaouiAbbassiyoussefKadaouiAbbassi

loop-patterns

Automate recurring tasks with interval-based loops, session-scoped schedules, and self-paced wakeups.

Community
Advanced