OpenClaw Auto‑Updater (Safe + Scheduled + Summary)
v1.0.0Schedule automatic OpenClaw and skill updates with reliable cron templates, timezone-safe scheduling, and clear summary outputs. Use for hands-off maintenance, scheduled upgrades, and concise update reports.
⭐ 12· 10.5k·99 current·104 all-time
byCodingPenguin44@dasweltall
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match what the instructions do: create cron entries (via openclaw cron add), run openclaw update and clawdhub update --all, and produce concise summaries. The skill requires no binaries, env vars, or installs beyond existing OpenClaw tooling, which is appropriate for an updater.
Instruction Scope
SKILL.md and the agent-guide are narrowly focused on detecting installation type, optionally creating a helper script under ~/.openclaw, configuring cron via openclaw cron add, running updates and producing a summary. The instructions reference only plausible config paths (~/.openclaw, logs) and standard package managers; they do not ask the agent to read unrelated system files or exfiltrate data.
Install Mechanism
Instruction-only skill with no install spec and no code files to write at install time. No external downloads, package installs, or archive extraction are requested.
Credentials
The skill declares no required environment variables, credentials, or unrelated config paths. The script and instructions operate on user-owned application files (home dir, .openclaw) which is proportionate to updating OpenClaw and its skills.
Persistence & Privilege
always is false and there is no install persistence. Note: the skill's recommended cron jobs will schedule recurring autonomous update actions (platform default allows the agent to invoke skills autonomously); this is expected for an auto-updater but has operational impact (automatic updates, possible gateway restarts) so users should weigh automatic execution vs manual control.
Assessment
This skill appears coherent and limited to scheduling OpenClaw and skill updates, but automatic updates can change runtime behavior and may restart services. Before enabling recurring runs: 1) run the dry-run variant first (clawdhub update --all --dry-run / openclaw update status) and inspect outputs; 2) review the optional helper script (~/.openclaw/scripts/auto-update.sh) and the log file it writes to (~/.openclaw/logs/auto-update.log) to ensure it does only what you expect; 3) schedule updates during off-hours and consider the "core only" or manual modes until you're confident; 4) maintain backups or snapshots if you rely on a stable gateway; and 5) if the skill's source is important to you, try to verify the publisher (source is unknown here) or reproduce the steps manually before enabling automation.Like a lobster shell, security has layers — review code before you run it.
auto-updatevk97fe0gxbnj2vaxpch0tv45ftn80e2hscronvk97fe0gxbnj2vaxpch0tv45ftn80e2hslatestvk97fe0gxbnj2vaxpch0tv45ftn80e2hsmaintenancevk97fe0gxbnj2vaxpch0tv45ftn80e2hsmonitoringvk97fe0gxbnj2vaxpch0tv45ftn80e2hsopenclawvk97fe0gxbnj2vaxpch0tv45ftn80e2hsopsvk97fe0gxbnj2vaxpch0tv45ftn80e2hsskillsvk97fe0gxbnj2vaxpch0tv45ftn80e2hsupdatesvk97fe0gxbnj2vaxpch0tv45ftn80e2hs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.