Auto-Updater (Gateway)
v1.0.1Schedule and run safe daily/weekly updates for Clawdbot + installed skills using the Gateway cron scheduler. Use when setting up "run updates at 04:00" jobs, rotating update reports, running `clawdhub update --all`, and (optionally) applying Clawdbot updates + restart + doctor.
⭐ 3· 1.9k·7 current·9 all-time
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 the runtime instructions: the SKILL.md explains setting up Gateway cron jobs that run clawdhub update --all and optionally clawdbot self-updates. The declared binary requirement (either clawdbot or clawdhub) is appropriate and proportionate.
Instruction Scope
Instructions stay within the updater automation scope. They include concrete example commands (including absolute example paths and a sample Telegram recipient ID). Be aware that the job's delivery options (channel + to) will transmit update summaries to whatever external endpoint you configure, which could disclose installed-skill/version info if sent to an untrusted recipient. The SKILL.md does not instruct reading unrelated system files or exfiltrating secrets, but users copying example absolute paths verbatim may unintentionally reference another user's filesystem/layout.
Install Mechanism
No install spec and no code files — instruction-only; nothing will be written to disk by the skill itself. This is the lowest-risk install posture.
Credentials
The skill declares no environment variables or credentials, which is consistent with its role as a config/workflow recipe. Note: runtime actions (clawdhub login, creating Gateway jobs that deliver to Telegram) do rely on existing logged-in accounts and delivery channel configuration outside the skill; that is expected but should be handled by the user/agent according to normal credential practices.
Persistence & Privilege
always:false and default invocation settings — the skill does not request permanent/always-on inclusion or elevated platform-wide privileges. It also does not modify other skills' configurations.
Assessment
This skill is a coherent how-to for scheduling automatic updates; it's not trying to hide unrelated access. Before installing or copying the example: 1) Verify clawdbot and clawdhub are the correct binaries on your system (don't blindly copy the example absolute paths). 2) Test with report-only mode first (do not enable self-update/restart) to confirm behavior. 3) Ensure the delivery channel/recipient you configure is trusted — update reports include version lists and could reveal internal state. 4) Be prepared for potential downtime if you enable Clawdbot self-updates and automatic restarts. If you need higher assurance, ask the skill author for a generic example (no user-specific paths/IDs) or for explicit checks the job will run before restarting services.Like a lobster shell, security has layers — review code before you run it.
automationvk978kzhbdd9prz2ftdjnfm5cq980baawcronvk978kzhbdd9prz2ftdjnfm5cq980baawlatestvk978kzhbdd9prz2ftdjnfm5cq980baawupdatesvk978kzhbdd9prz2ftdjnfm5cq980baaw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔄 Clawdis
OSWindows · macOS · Linux
Any binclawdbot, clawdhub
