cron_skill

This skill helps you manage Codex automations by editing the local SQLite store and filesystem configs, enabling fast creation, updates, and runs.

Python

42

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill tkersey/dotfiles --skill cron

SKILL.md6.6 KB

Overview

This skill manages Codex app automations stored in the local SQLite DB (~/.codex/sqlite/codex-dev.db) and the synced filesystem automation configs. It provides commands to add, list, update, enable/disable, delete, and run automations immediately, plus utilities to run due jobs headless via a LaunchAgent or single-run runner.

How this skill works

Operations are performed via the bundled scripts/cron.py which edits the automations table and syncs minimal filesystem config. Scheduling uses RFC5545 RRULE strings (prefixed with RRULE:), and a headless runner scripts/automation_runner.py executes due automations and records last_run_at/next_run_at and individual automation_runs rows. Installable LaunchAgent wrappers provide periodic execution without the desktop app.

When to use it

Add a new periodic automation with a prompt and RRULE schedule
Inspect automation records when a scheduled job didn't run or produced unexpected output
Update schedule, prompt, name, or working directories (cwd) for an existing automation
Enable or disable automations during testing or deployment windows
Run a specific automation immediately for debugging or one-off needs

Best practices

Always supply RFC5545 RRULE strings including BYHOUR and BYMINUTE for stable schedules
Use --prompt-file for multi-line prompts to avoid shell quoting issues
Keep cwds explicit; default is the repo root—confirm paths when ambiguous
Make minimal, explicit edits so filesystem and DB stay in sync
Use run-now and the headless runner to validate behavior before relying on the scheduler

Example use cases

Create a daily standup summary: create with prompt file and RRULE:FREQ=DAILY;BYHOUR=9;BYMINUTE=0
Draft weekly release notes: create or update an automation with RRULE:FREQ=WEEKLY;BYDAY=FR;BYHOUR=9;BYMINUTE=0
Temporarily disable an automation during a freeze using disable --id <id>
Force immediate execution of a flaky automation with run-now --id <id> to collect logs
Install the LaunchAgent for unattended execution and check logs at ~/Library/Logs/codex-automation-runner

FAQ

No. Only RFC5545 RRULE strings are supported. Include the RRULE: prefix to match stored records.

How do I provide multi-line prompts?

Use --prompt-file pointing to a file containing the full prompt to avoid quoting issues.

Can I run automations without the desktop app?

Yes. Install the LaunchAgent via scripts/install_launch_agent.sh or run scripts/automation_runner.py --once for headless execution.