cron
Skill17 starsChanged 8 months agoMITView on GitHub
Manage recurring schedules via OS-native schedulers (launchd on macOS, crontab on Linux/WSL)
6 other projects use a version of this.
Adopted by
Most recently taken up by
- EthanLLL/loomtheir own version, first seen Nov 8, 2026
- oidsdev/honeypottheir own version, first seen Oct 15, 2026
- thedigitalorganizer/soloshiptheir own version, first seen Oct 15, 2026
- superbereza/lobster-powerstheir own version, first seen Oct 11, 2026
- TheLatentSpaceLab/Qubitotheir own version, first seen Apr 1, 2026
- iceycc/icey-skillstheir own version, first seen Feb 21, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- EthanLLL/loom★ 4same name
- iceycc/icey-skills★ 4same name
- TheLatentSpaceLab/Qubito★ 1same name
- oidsdev/honeypot★ 0same name
- superbereza/lobster-powers★ 0same name
- thedigitalorganizer/soloship★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- release-cekernelSkill
- atSkill
- dispatchSkill
- orchctlSkill
- orchestrateSkill
- postmortemSkill
- probeSkill
- setupSkill
- unix-architectSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Read skills/references/namespace-detection.md from the repository root ($(git rev-parse …
- Very specific: line 35
If the user provides all required options (--label and --schedule), pass them directly.
- Distinctive: line 37
If any required option is missing, interactively ask the user for the missing values before executing:
- Very specific: line 42
If both given, --prompt takes precedence.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/cron
Manage recurring scheduled execution of cekernel dispatch. Uses OS-native schedulers (launchd on macOS, crontab on Linux/WSL).
Usage
/cron register --schedule "<cron-expr>" [--label <label>] [--prompt <prompt>] [--repo <path>]
/cron list
/cron cancel <id>Note: In plugin mode, /cekernel:cron also works.
Workflow
Step 1: Detect Namespace and Determine Script Location
- Read
skills/references/namespace-detection.mdfrom the repository root ($(git rev-parse --show-toplevel)/skills/references/namespace-detection.md). If the Read fails (file not found), you are in plugin mode. - Execute the detection Bash snippet from the reference file.
- Set the script path based on the result:
- If
CEKERNEL_NS=local:CRON_SH="$(git rev-parse --show-toplevel)/scripts/scheduler/cron.sh" - If
CEKERNEL_NS=plugin:CRON_SH="$(dirname "$(dirname "$(which spawn-worker.sh 2>/dev/null)")")/scripts/scheduler/cron.sh"
- If
Step 2: Execute Command
register — Interactive Option Builder
If the user provides all required options (--label and --schedule), pass them directly.
If any required option is missing, interactively ask the user for the missing values before executing:
--labelor--prompt(one required): Ask whether to use a dispatch label or a custom prompt.--label <label>— Shorthand: generates prompt"/dispatch --env headless --label <label>"for theclaude --bgsession--prompt <prompt>— Arbitrary prompt string passed directly to theclaude --bgsession- If both given,
--prompttakes precedence.
--schedule(required): Ask for a cron expression. Show common examples to help the user:0 9 * * 1-5— Weekdays at 9:00 AM0 9 * * *— Every day at 9:00 AM30 */6 * * *— Every 6 hours at :300 0 * * 0— Every Sunday at midnight- Format:
minute hour day-of-month month day-of-week
--repo(optional): Ask if the target repository is the current directory. If not, ask for the path.
Once all values are gathered, confirm the full command with the user, then execute.
list / cancel
Pass directly to cron.sh:
bash "$CRON_SH" register --label "ready" --schedule "0 9 * * 1-5"
bash "$CRON_SH" list
bash "$CRON_SH" cancel cekernel-cron-a1b2c3Step 3: Present Results
- For
register: The script outputs registration details. Confirm to the user. - For
list: The script outputs a formatted table. Show it directly. Entries marked[drifted]were removed from the OS scheduler externally — suggest re-registering or cancelling. - For
cancel: The script confirms cancellation. Relay to the user. - On errors: Show the error message and suggest corrective action.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

