OpenClaw Auto-Updater

v1.0.1

Automatically keep OpenClaw and installed workspace skills up to date using native OpenClaw commands. Use when the user wants automatic update checks, schedu...

0· 82·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the SKILL.md: instructions only call native openclaw commands and cron scheduling. There are no unrelated env vars, binaries, or installs requested.
Instruction Scope
Runtime instructions are limited to running openclaw commands and creating cron jobs (using openclaw cron or standard cron). The skill explicitly avoids legacy tools and requires user approval for elevated actions. It does not instruct reading unrelated files or exfiltrating data.
Install Mechanism
No install spec and no code files — nothing is downloaded or written by the skill itself. This is the lowest-risk model for a helper that documents CLI usage.
Credentials
The skill requests no environment variables, credentials, or config paths. All suggested actions use local openclaw commands and cron; no external secrets are required.
Persistence & Privilege
The skill recommends creating cron jobs (persistent scheduled tasks) using openclaw cron. This is expected for an auto-updater but means the agent (or user) will create persistent system jobs; the skill itself is not marked always:true and requests no elevated credentials in the bundle.
Assessment
This skill is an instruction-only helper for the OpenClaw CLI and is internally consistent. Before installing or running it, confirm that: (1) you have the openclaw CLI available and understand the openclaw cron commands it will run, (2) you want persistent cron jobs created on your system (the templates create scheduled tasks), (3) you prefer automatic skill updates but keep core OpenClaw updates opt-in unless you explicitly allow full auto-updates, and (4) any job creation is performed with appropriate user consent and permissions. If you want stronger control, instruct the agent to only produce the cron commands for you to review/run manually rather than creating jobs autonomously.

Like a lobster shell, security has layers — review code before you run it.

latestvk973y2crpn0xk1ywaxgr55fkmd83kt1x

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🔄 Clawdis
OSWindows · Linux · macOS

Comments