cron-management

Restore, persist, and troubleshoot recurring crons via config.json.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MrWest3/west-command-center --skill cron-management-mrwest3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron-management
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/cron-management
Command: npx skills add https://github.com/MrWest3/west-command-center --skill cron-management-mrwest3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crons die on restart — this skill ensures recurring tasks survive restarts by offering creation, restoration, and persistence via config.json, with tooling to fix missing or failed schedules.

Core Features & Use Cases

  • Create recurring crons that persist across restarts
  • Restore lost crons from config.json on startup
  • Diagnose and fix non-firing schedules and duplicates
  • Use Case: When deploying a new release, ensure scheduled jobs resume automatically

Quick Start

Run CronList to verify active crons and then create or restore recurring tasks using CronCreate or the /loop command.

Frequently Asked Questions about cron-management

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

FAQPage Schema
How do I keep recurring cron tasks running after a server restart?

To keep recurring crons running after a restart, the skill persists all schedules to config.json first and automatically restores them on startup, ensuring your recurring tasks survive unexpected downtime and resume without manual intervention.

Why does my scheduled workflow stop firing after modifying config.json?

Your scheduled workflow may stop firing if the config.json is modified incorrectly or crons are not written to the file first. You can diagnose missing schedules and troubleshoot non-firing workflows using dedicated diagnostic commands to restore proper execution.

What is the best way to manage recurring tasks and automate schedule restoration?

The best way to manage recurring tasks is to use a centralized command interface like CronList, CronCreate, and CronDelete to handle scheduling, which automatically persists configurations to config.json and restores them on startup for robust automation.

Can I use /loop to create and restore recurring crons automatically?

Yes, you can use the /loop command to create recurring crons that are automatically persisted to config.json and restored on startup, providing a straightforward method to maintain and recreate automated schedules.

How do I diagnose duplicate crons or non-firing schedules in my workflow?

To diagnose duplicate crons or non-firing schedules, you can run CronList to verify active crons and identify inconsistencies, then use troubleshooting commands to fix missing schedules and remove duplicates from your config.json configuration.