ClawHub

Cron Local

v1.0.0

Local-first recurring schedule engine for reminders, repeated tasks, and time-based execution plans. Use whenever the user mentions recurring timing, repetit...

⭐ 0· 81·0 current·0 all-time
by@morrison230·duplicate of @panchenbo/cron-scheduler-local·canonical: @projectsnowwork/cron
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the included scripts: adding/listing/pausing/resuming jobs and computing next runs. Required resources (python3, local files under ~/.openclaw/workspace/memory/cron) are consistent with a local scheduler.
✓
Instruction Scope
SKILL.md instructs use of python3 and local storage paths; the scripts only read/write the declared JSON files and do not access other system config, environment variables, or external endpoints. Behavior stays within the stated purpose.
✓
Install Mechanism
No install spec; this is an instruction-plus-scripts bundle that requires no network downloads or package installs. All code is included in the package.
✓
Credentials
The skill requests no environment variables or credentials. It stores data under the user's home directory, which is appropriate for a local scheduler.
✓
Persistence & Privilege
The skill is not marked always:true and does not modify other skills or system-wide agent settings. It persists only its own data files under ~/.openclaw/workspace/memory/cron.
Assessment
This skill appears to be a straightforward, local-only scheduler. Before installing: ensure you are comfortable with the skill writing to ~/.openclaw/workspace/memory/cron (jobs.json, runs.json, stats.json) and that python3 is available. The code is included and contains no network calls or credential access. Consider backing up any existing ~/.openclaw/workspace/memory/cron files if you already use that folder. Note: the scripts manage schedules but do not run external tasks or integrate with cloud services — they only record and compute next-run timestamps. If you need automatic execution of commands at run time, that capability is not present and would require additional tooling (which would expand the security surface).

Like a lobster shell, security has layers — review code before you run it.

latestvk97b24aqgmg9pr5kzdtrespned838zbw

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments