Scheduler

v2.0.0

Scheduler - command-line tool for everyday use Use when you need scheduler.

1· 1.8k·17 current·17 all-time
byBytesAgain2@ckchzh

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for ckchzh/scheduler.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Scheduler" (ckchzh/scheduler) from ClawHub.
Skill page: https://clawhub.ai/ckchzh/scheduler
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install scheduler

ClawHub CLI

Package manager switcher

npx clawhub@latest install scheduler
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & 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
1.8kdownloads
1stars
4versions
Updated 1mo ago
v2.0.0
MIT-0

Scheduler

Task scheduler — cron job management, recurring tasks, calendar integration, reminder setting, deadline tracking, and time blocking.

Commands

CommandDescription
scheduler runExecute main function
scheduler listList all items
scheduler add <item>Add new item
scheduler statusShow current status
scheduler export <format>Export data
scheduler helpShow help

Usage

# Show help
scheduler help

# Quick start
scheduler run

Examples

# Run with defaults
scheduler run

# Check status
scheduler status

# Export results
scheduler export json

How It Works

Tips

  • Run scheduler help for all commands
  • Data stored in ~/.local/share/scheduler/

Powered by BytesAgain | bytesagain.com Feedback & Feature Requests: https://bytesagain.com/feedback

Comments

Loading comments...