cron-management

To persist cron tasks across restarts, you enforce a strict config.json as the source of truth. This skill restores and reconciles cron definitions automatically by reading that config file after session failures or restarts.

Restoring recurring crons after a restart involves reading the saved cron definitions from config.json and relaunching them with the appropriate commands. This skill reconciles the active cron state against the config file.

Yes, you can schedule both recurring and one-shot cron jobs by adding their definitions to config.json. This skill supports creating both task types and enforces the config file as the strict truth for all scheduled workflows.

To troubleshoot expired or duplicate crons, you update the cron definitions in config.json and delete the unwanted entries. This skill provides clear procedures for removing stale crons and ensuring persistence in dynamic environments.

Scheduled reminders stop working after a restart if they are not persisted in a config.json file. This skill solves the problem by using config.json as strict truth to restore and relaunch cron definitions across sessions.