Schedule
v1.0.2Program recurring or one-time tasks. User defines what to do, skill handles when.
⭐ 3· 4.1k·28 current·29 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (scheduling tasks) align with what the skill asks for: local storage under ~/schedule, job definitions, and timing behavior. It does not request unrelated credentials or system-wide changes.
Instruction Scope
SKILL.md stays within scheduling scope: it instructs creating ~/schedule, persisting jobs, confirming permissions, and executing only user-defined tasks. One ambiguity: it states it 'handles WHEN' but gives no implementation details (background scheduler vs. platform timer). That is an operational assumption rather than a security mismatch, but you should confirm how the agent/platform will actually trigger jobs.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest-risk install surface. Nothing is downloaded or written beyond the documented ~/schedule files.
Credentials
No environment variables, credentials, or external config paths are required. The skill documents an explicit 'requires' field per job to list other skills the job needs, which is appropriate and limited.
Persistence & Privilege
always:false (normal). The skill allows autonomous invocation (platform default), which is required for scheduled execution on many platforms; this is reasonable but increases blast radius if you later grant it broad permissions or link jobs to other skills. The skill does not request permanent system-wide changes.
Assessment
This skill appears coherent for scheduling, but verify two operational points before installing: (1) confirm how scheduled execution is actually triggered on your platform (background agent, platform scheduler, or manual invocation), because SKILL.md assumes timing support but provides no installer/service; (2) be careful about the 'requires' permissions you grant to jobs — scheduled jobs will run later and may call other skills that have access to your data (email, files, etc.). Review ~/schedule/jobs.json regularly, avoid storing secrets directly in job 'task' text, and ensure you can list/cancel jobs and revoke granted permissions.Like a lobster shell, security has layers — review code before you run it.
latestvk9793yvgv8h16vtfx2mzwes6rd819j0e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📅 Clawdis
OSLinux · macOS · Windows