Scheduler
v2.0.0Scheduler - command-line tool for everyday use Use when you need scheduler.
⭐ 1· 1.1k·14 current·14 all-time
byBytesAgain2@ckchzh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (scheduler/cron-like task manager) matches the code's behavior: it records tasks and events to log files under ~/.local/share/scheduler and provides commands for add/plan/track/export/status. There are no unrelated requirements (no env vars or external services).
Instruction Scope
SKILL.md describes basic scheduler commands and data storage location, which aligns with the script's behavior. Minor mismatch: SKILL.md lists commands such as 'scheduler run' and 'scheduler list' while the visible script implements many commands like add/plan/track/prioritize; this is a documentation vs implementation inconsistency but not inherently dangerous. The instructions and script operate on user files in the home directory (~/.local/share/scheduler) — expected for this tool.
Install Mechanism
No install spec; this is effectively an instruction-only skill with a small shell script. No downloads or package installs are performed by the skill itself.
Credentials
The skill requires no environment variables or credentials. The script uses $HOME to create and read files in the user's home directory — appropriate for a local scheduler tool.
Persistence & Privilege
The skill is not always-enabled and does not request elevated privileges. It persists data to its own path under the user's home directory and does not modify other skills or system-wide configs in the visible code.
Assessment
This appears to be a straightforward, local scheduler that stores data at ~/.local/share/scheduler and does not ask for secrets or network access in the visible code. Before installing or running: (1) review the full scripts/script.sh file (the provided listing was truncated) to ensure there are no hidden network calls or commands later in the file; (2) run it in a sandbox or isolated account if you want to be cautious; (3) note that it will create and write log files under ~/.local/share/scheduler — back up or inspect that folder if you care about privacy; (4) if documentation and implemented commands differ, expect minor discrepancies but verify the commands you intend to use.Like a lobster shell, security has layers — review code before you run it.
latestvk974ptzvrjbqsk1jy9jp606bcn833pcr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.