Cron
v1.0.0Local-first recurring schedule engine for reminders, repeated tasks, and time-based execution plans. Use whenever the user mentions recurring timing, repetit...
⭐ 5· 4.6k·62 current·66 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included Python scripts: add/list/pause/resume/show/next-run with local JSON storage. The requirement of python3 and the lack of network/third-party credentials are proportionate to a local schedule engine.
Instruction Scope
SKILL.md runtime instructions and the scripts only read/write the declared local storage files and do not reference other system config, credentials, or external endpoints. No vague 'gather context' directives are present.
Install Mechanism
No install spec (instruction-only) and included scripts are plain Python files. Nothing is downloaded or extracted from external URLs.
Credentials
No environment variables or external credentials requested. The code uses the user's home directory (~) for storage, which is appropriate for a local-first scheduler.
Persistence & Privilege
always is false, the skill does not modify other skills or system-wide settings and only creates/updates files under its own ~/.openclaw workspace path.
Assessment
This appears to be a simple, local-only Python-based scheduler. It will create and update files under ~/.openclaw/workspace/memory/cron (jobs.json, runs.json, stats.json); review whether you’re comfortable with those files being created there. No network or external credentials are used. Notes: the code uses naive datetime objects (no timezone-aware handling), so scheduled times may not handle DST/timezone transitions precisely; the default timezone string in add_job.py is 'Asia/Tokyo' but it is only stored as metadata and not enforced. If you want to be extra cautious, inspect the scripts locally before running and run scripts/init_storage.py first to see the created files. Overall internal coherence is good and I see no signs of data exfiltration or unrelated privilege requests.Like a lobster shell, security has layers — review code before you run it.
latestvk9744axgt0n3f0zw9wr0je51jn82r9tb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.