← Back to Skills Marketplace
Dial A Cron
by
agenthyjack
· GitHub ↗
· v2.0.0
· MIT-0
104
Downloads
0
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install dial-a-cron
Description
Stateful cron system for OpenClaw with persistent memory, change detection, smart routing, token budget tracking, and self-healing. Requires 'openclaw' and '...
README (SKILL.md)
dial-a-cron
Stateful cron system with memory, change detection, smart delivery, token budget tracking, and self-healing.
Security & Review Requirements (per OpenClaw scanner)
This skill has broad I/O capabilities and is marked Suspicious (high confidence) by the OpenClaw scanner.
Before installing or using:
- Audit all job configs (especially
diffsfor file/command/HTTP reads androutesfor webhook URLs, target_id). - Run in an isolated environment with limited network access (consider denying outbound webhooks if you do not want potential exfiltration).
- Ensure
openclawandgogCLIs exist and run with least privilege. - Whitelist HTTP targets and restrict diff file paths to specific safe directories. Avoid diffs on secrets or system files.
- The code uses
subprocess.run(..., shell=True)with values from job configs and outputs — unsanitized fields could allow shell injection. - The skill can read arbitrary local files, make HTTP requests (including to internal IPs), and post outputs to external endpoints.
- Persisted state/logs may contain sensitive data from jobs — review storage permissions.
Full scanner report is in references/security-review.md.
Only use if you have reviewed the code and trust the job configs.
Basic Usage
openclaw cron create --name my-job --command "your-command" --dial "state:yes,change-detection:yes,routing:telegram:error,slack:warning,budget:50000,self-heal:yes"
What it contains
- Persistent state and change detection
- Smart delivery routing (webhook, message, email, etc.)
- Token budget tracking
- Self-healing (retries, backoff, auto-pause)
- Preflight, diff, router, and state scripts
- Requires
openclawandgogCLIs (not declared in older versions — now explicit)
No credentials are requested, but the code can contact arbitrary endpoints if job configs allow it.
Installation
openclaw skills install dial-a-cron
Then review the scripts in scripts/ and all job configs before creating any scheduled jobs.
Security Notes (from scanner)
- The skill implements the advertised features but has disproportionate I/O for a simple cron wrapper.
- Missing declared dependencies (openclaw, gog) in older metadata.
- Potential for exfiltration of local file contents or command output via routes/webhooks.
- Shell command injection risk if job configs or outputs are not sanitized.
- Persistence of state/logs that may contain sensitive job output.
Review the code, restrict job configs, and run in an isolated environment with network controls.
Full details and the exact scanner report are in references/security-review.md.
Version: 1.0.1 (security audit and full disclosure) License: MIT-0
Clean, honest, and auditable. Review before use.
Usage Guidance
This skill appears to implement the advertised features but requires careful handling. Before installing:
- Audit every job config (jobs/*.json). Pay special attention to 'diffs' (file paths, commands, URLs) and 'routes' (webhook URLs, target_id) and remove any targets you don't trust.
- Treat job configs as privileged: do not point diffs at secrets or system files. Avoid command diffs unless you control the commands.
- Run Dial-a-Cron in an isolated/containerized environment with egress controls; consider blocking outbound webhooks unless explicitly whitelisted.
- Ensure openclaw and gog CLIs exist and run with least privilege; verify credential use for those tools.
- Look for subprocess.run(..., shell=True) usages in the code (router.py, diff.py, others) and either sanitize/escape all inputs or modify code to use argument arrays (shell=False).
- If you cannot audit and control job configs and network access, do not install in a production environment. If in doubt, run the scripts in a disposable VM/container and monitor network and file activity.
Capability Analysis
Type: OpenClaw Skill
Name: dial-a-cron
Version: 2.0.0
The skill provides a powerful stateful cron system but exhibits high-risk capabilities including arbitrary shell execution (subprocess.run with shell=True), arbitrary file reads, and network exfiltration via webhooks and emails in scripts/diff.py and scripts/router.py. While the bundle includes an unusually transparent security self-audit (references/security-review.md) and warns the user of these risks in SKILL.md, the lack of input sanitization and the broad I/O scope represent significant vulnerabilities that could be exploited if job configurations are mismanaged.
Capability Assessment
Purpose & Capability
The name/description (stateful cron with diffs, routing, budgets, self-heal) match the included scripts. However the skill metadata declares no required binaries or credentials while the code explicitly shells out to external CLIs (openclaw and gog) and expects optional env vars (DAC_JOBS_DIR, DAC_STATE_DIR, DAC_LOG_DIR). Missing declared dependencies is an incoherence: an operator would reasonably expect required CLIs/credentials to be declared.
Instruction Scope
SKILL.md and preflight instructions instruct the agent/operator to run preflight and inject DAC_CONTEXT into LLM prompts. The preflight/diff engine can read arbitrary local files, run arbitrary commands, and fetch arbitrary HTTP URLs defined in job configs; those results can be placed into DAC_CONTEXT and routed to external webhooks or emailed. The runtime instructions therefore allow collection and transmission of local file contents and command outputs — scope is broader than a minimal cron wrapper and is high-risk unless job configs are strictly controlled.
Install Mechanism
No install spec (instruction-only) — the bundle contains Python scripts but nothing is downloaded or auto-executed by an installer. This lowers supply-chain risk; however consumers receive executable scripts that must be run locally and therefore must be audited before execution.
Credentials
The skill declares no required env vars or credentials, yet the code reads optional env vars (DAC_JOBS_DIR, DAC_STATE_DIR, DAC_LOG_DIR) and shells out to external CLIs that typically require credentials (openclaw, gog). It also accepts webhook URLs, file paths, and agent endpoints from job configs. The absence of declared dependencies/credentials is disproportionate and could mislead operators about runtime capabilities and privileges.
Persistence & Privilege
The skill persists state, logs, and memory under local directories (state/, memory/, logs/). 'always' is not set. Persisted files may contain sensitive outputs or carry data from jobs; this is expected for a stateful cron but operators should review storage locations and permissions.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install dial-a-cron - After installation, invoke the skill by name or use
/dial-a-cron - Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.0
Full security overhaul per OpenClaw scanner (high confidence Suspicious). Added complete honest disclosure of risks (arbitrary file reads, HTTP to any URL, shell injection potential, undeclared CLIs openclaw/gog). Strong review/audit warnings, isolated environment recommendations, whitelist advice, and full scanner report in references/security-review.md. No misleading metadata. Completely transparent.
v1.0.2
Intelligent stateful cron system with persistent memory, change detection (skip if no change), smart delivery routing, token budget tracking, and self-healing with auto-pause. Turns basic fire-and-forget crons into reliable, self-aware jobs.
v1.0.1
**Changelog for dial-a-cron 1.0.1**
- Major restructuring: moved core scripts from `src/` to `scripts/`, removed job/sample data files.
- Added documentation (`README.md`, `job-config-schema.md`) and improved skill metadata.
- Consolidated and cleaned up codebase for clarity and production-readiness.
- Updated usage and installation instructions for streamlined OpenClaw integration.
v1.0.0
Intelligent stateful cron system with change detection, smart delivery routing, token budget tracking, and self-healing. Replaces basic fire-and-forget crons with reliable, self-aware jobs.
Metadata
Frequently Asked Questions
What is Dial A Cron?
Stateful cron system for OpenClaw with persistent memory, change detection, smart routing, token budget tracking, and self-healing. Requires 'openclaw' and '... It is an AI Agent Skill for Claude Code / OpenClaw, with 104 downloads so far.
How do I install Dial A Cron?
Run "/install dial-a-cron" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Dial A Cron free?
Yes, Dial A Cron is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Dial A Cron support?
Dial A Cron is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Dial A Cron?
It is built and maintained by agenthyjack (@agenthyjack); the current version is v2.0.0.
More Skills