Cron Scheduler Local

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

Security Scan

The skill is internally consistent with its stated purpose: it implements a local-only cron/scheduler using Python and only writes to a dedicated workspace directory; no network calls, secret access, or unusual installs are requested.

Purpose & Capability

Name, description, and included scripts align: the bundle provides local scheduling (add/list/pause/resume/next) and stores data under ~/.openclaw/workspace/memory/cron. No extra binaries or credentials are requested. Minor metadata oddity: the ownerId in _meta.json differs from the top-level registry Owner ID in the provided metadata — this could indicate repackaging or a metadata mismatch but does not change the code's behavior.

Instruction Scope

SKILL.md and the scripts confine actions to parsing schedule data and reading/writing the declared JSON files. Instructions require python3 and explicitly state 'no external sync'. The runtime code does not access environment variables, system-wide configs, or external endpoints. One functional note: resume_job assumes compute_next_run returns a datetime and calls .isoformat(); if compute_next_run returns None in some edge cases the script may error — this is a robustness bug, not malicious behavior.

Install Mechanism

There is no install spec or external downloads; this is effectively instruction- and script-only. All code is included in the package and nothing is fetched from the network or a third-party registry during install.

Credentials

The skill requests no environment variables, no credentials, and only uses the user's home directory under ~/.openclaw/workspace/memory/cron. There are no secret-like env names or unrelated credential requirements.

Persistence & Privilege

always is false and the code only creates/updates files within its own workspace path (jobs.json, runs.json, stats.json). It does not modify other skills' configs or system-wide settings.

Assessment

This skill appears to do what it says: local scheduling with data stored under ~/.openclaw/workspace/memory/cron and no network access. Before installing, consider: 1) Verify the publisher/source because the metadata contains a minor ownerId mismatch; if you don't trust the author, inspect the included Python scripts yourself. 2) The skill will create and persist JSON files in your home workspace — if that directory can contain sensitive info for you, consider isolating the skill (container or separate account) or moving the storage path. 3) There is a small robustness bug (resume may crash if next-run can't be computed); this is functional, not a security concern. If you trust the source and are comfortable with local persistent storage, the package is coherent and proportionate to its purpose.

Cron

Turn recurring intentions into structured local schedules.

Core Philosophy

1. Repetition should be captured once, then trusted.
2. A schedule is not just a reminder — it is an execution contract over time.
3. The system should make recurrence visible, editable, and pausable.
4. Users should always know what runs next.

Runtime Requirements

• Python 3 must be available as python3
• No external packages required

Storage

All data is stored locally only under:

• ~/.openclaw/workspace/memory/cron/jobs.json
• ~/.openclaw/workspace/memory/cron/runs.json
• ~/.openclaw/workspace/memory/cron/stats.json

No external sync. No cloud storage. No third-party cron service.

Job Status

• active: schedule is live
• paused: temporarily disabled
• archived: no longer active, kept for history

Schedule Types

• daily
• weekly
• monthly
• interval

Key Workflows

• Capture recurring job: add_job.py
• See what runs next: next_run.py
• Pause or resume: pause_job.py, resume_job.py
• Inspect one job: show_job.py
• Review all jobs: list_jobs.py