← Back to Skills Marketplace
indigas

Cron Manager

by Indigas · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
144
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install cron-manager
Description
Manage, schedule, monitor, and report on recurring cron tasks with flexible patterns and handle dependencies, priorities, timezones, and execution logs.
README (SKILL.md)

CLAW CRON MANAGER

You are a cron-manager skill that handles scheduling, monitoring, and management of recurring tasks for autonomous agents running on OpenClaw.

What You Do

  • Create, schedule, and manage cron tasks with flexible patterns (hourly, daily, weekly, custom intervals)
  • Monitor cron execution, track success/failure rates, and alert on issues
  • Provide task history, statistics, and performance reports
  • Manage task dependencies, priorities, and resource limits
  • Generate cron expressions and human-readable schedules
  • Handle timezones, DST transitions, and scheduling conflicts

What You Don't Do

  • Execute the actual task logic (that's the task's job)
  • Modify system crontabs or system-level scheduling
  • Access external services beyond the OpenClaw API
  • Guarantee execution during system downtime or maintenance windows

Available Commands

Run from the scripts/cron_manager.py script with these actions:

  • cron list [--status all|active|paused|failed] — List all cron tasks
  • cron show \x3Ctask_id> — Show detailed task info and recent runs
  • cron add \x3Cname> --command "\x3Ccmd>" --schedule "\x3Cpattern>" [--timezone UTC] — Add a new task
  • cron remove \x3Ctask_id> — Delete a task
  • cron pause \x3Ctask_id> — Pause execution without deleting
  • cron resume \x3Ctask_id> — Resume a paused task
  • cron run \x3Ctask_id> — Force run a task immediately
  • cron logs \x3Ctask_id> [--count 10] — View recent execution logs
  • cron stats [--hours 168] — Show execution statistics for a period
  • cron health — Overall system health check

Schedule Format

Use standard cron patterns:

  • * * * * * — Every minute
  • */5 * * * * — Every 5 minutes
  • 0 * * * * — Every hour
  • 0 0 * * * — Daily at midnight
  • 0 0 * * 1 — Weekly on Monday
  • 0 0 1 * * — Monthly on 1st
  • @hourly, @daily, @weekly, @monthly, @yearly — Shorthand

Or human-friendly patterns:

  • "every 30 minutes"
  • "daily at 9am"
  • "weekly on Monday at 10am"
  • "every Monday, Wednesday, Friday at 8am"

Example Usage

# Add a daily cleanup task
./cron_manager.py add "cleanup" --command "python cleanup.py" --schedule "@daily"

# Check status of all tasks
./cron_manager.py list --status active

# View logs for a specific task
./cron_manager.py logs "cleanup" --count 5

# Check overall health
./cron_manager.py health

Output Format

All commands return JSON with standardized fields:

{
  "status": "success",
  "data": {
    "tasks": [
      {
        "id": "cleanup",
        "name": "Daily Cleanup",
        "status": "active",
        "schedule": "@daily",
        "next_run": "2026-04-18T00:00:00Z",
        "last_run": "2026-04-17T00:00:01Z",
        "success_rate": 0.98
      }
    ]
  }
}
Usage Guidance
This skill is mostly coherent with its description but contains two practical security concerns you should evaluate before installing or using it: 1) Arbitrary shell execution: The script executes task commands via subprocess.run(..., shell=True). That means any task stored in tasks.json can run arbitrary shell commands with the same privileges as the agent. Only add tasks that you fully trust, and do not allow untrusted agents or users to create/modify tasks. Consider sandboxing execution, avoiding shell=True, or using safe execution wrappers. 2) Path traversal / file operations on task IDs: Task IDs are used directly in filenames (logs and removals) without sanitization. A crafted task_id (e.g., containing ../) could cause the script to read, write, or remove files outside the intended data directory if filesystem permissions allow. Validate/sanitize task IDs and consider restricting CRON_DATA_DIR to a locked directory with proper permissions. Other notes: the schedule parsing and next-run calculation are simplistic and have edge-case bugs (could be CPU-heavy for some inputs). Logs and commands are stored in plaintext under the user's home by default — treat the data directory as sensitive. If you proceed, run the skill in a restricted environment, review tasks.json and logs before executing 'run' actions, and consider patching the script to sanitize IDs and avoid shell=True.
Capability Analysis
Type: OpenClaw Skill Name: cron-manager Version: 1.0.0 The skill provides a local task management system that allows for the scheduling and execution of arbitrary shell commands. The primary risk is found in `scripts/cron_manager.py`, which uses `subprocess.run(shell=True)` to execute commands stored in `tasks.json`. While this functionality is consistent with the stated purpose of a cron manager, the lack of command sanitization and the use of a shell environment represent a high-risk capability that could be easily exploited via prompt injection to achieve Remote Code Execution (RCE). No evidence of intentional malice, such as hardcoded backdoors or data exfiltration, was found.
Capability Assessment
Purpose & Capability
Name, description, SKILL.md, and the included script are consistent: a file-based cron manager that stores tasks and logs under a per-skill data directory and exposes CLI actions to list, add, remove, run, etc. The required environment/installation footprint is minimal and matches the stated functionality.
Instruction Scope
SKILL.md instructs operators to run scripts/cron_manager.py and the script implements the described commands. However the runtime instructions (and the script) allow executing arbitrary commands provided in task definitions and reading/writing files in a data directory; SKILL.md's assurances (e.g., 'Do not modify system crontabs') are respected, but the agent will run user-provided shell commands on demand — this is expected for a scheduler but is a sensitive capability and should be handled carefully.
Install Mechanism
Instruction-only skill with no install spec. Nothing is downloaded or written by an installer; the only code is the included script. This is low install risk.
Credentials
No required credentials or config paths are declared. The script optionally respects a CRON_DATA_DIR env var (reasonable). There are no requests for unrelated secrets or external service credentials in the manifest or SKILL.md.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It writes only to a per-skill data directory (by default under the user's home). Autonomous invocation is allowed by default but not unusual; that alone is not flagged.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install cron-manager
  3. After installation, invoke the skill by name or use /cron-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of cron-manager for OpenClaw. - Provides flexible scheduling, monitoring, and management of recurring tasks for autonomous agents. - Supports task creation, scheduling, pause/resume, manual runs, and deletion. - Tracks execution history, success/failure rates, and offers health/stats reporting. - Handles task dependencies, priorities, resource limits, timezones, and DST. - Offers standardized JSON output for all commands and both cron and human-friendly schedule input.
Metadata
Slug cron-manager
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Cron Manager?

Manage, schedule, monitor, and report on recurring cron tasks with flexible patterns and handle dependencies, priorities, timezones, and execution logs. It is an AI Agent Skill for Claude Code / OpenClaw, with 144 downloads so far.

How do I install Cron Manager?

Run "/install cron-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Cron Manager free?

Yes, Cron Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Cron Manager support?

Cron Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Cron Manager?

It is built and maintained by Indigas (@indigas); the current version is v1.0.0.

💬 Comments