Auto Updater Backup
v1.0.0Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of w...
⭐ 0· 56·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name/description (auto-update Clawdbot and skills) aligns with the runtime instructions: adding a cron job, running package manager commands (npm/pnpm/bun) or source update, running `clawdbot doctor`, and calling `clawdhub update --all`. Checks for install type (global vs source) and the commands used are appropriate for performing those updates.
Instruction Scope
Instructions reference creating a helper script under ~/.clawdbot, writing logs, and adding a cron job via `clawdbot cron add`. Those actions are within scope. One note: the script captures and forwards raw command output (skill_output) in the update summary — this may include error messages or other command output. Users should be aware the report can include whatever the update commands print.
Install Mechanism
This is an instruction-only skill with no install spec and no code files executed at install time. That minimizes installer risk; actions happen only when you run the commands / cron job executes.
Credentials
No environment variables, credentials, or unrelated config paths are requested. The script writes to user-owned paths under the user's HOME (~/.clawdbot) and uses system package managers as expected for updating — this is proportionate to the stated purpose.
Persistence & Privilege
The skill recommends adding a cron job (user-level via `clawdbot cron add`) and creating user-local scripts/logs. always is false and it doesn't request system-wide modifications or other skills' configs. This level of persistence is expected for an auto-updater.
Assessment
This skill appears coherent with its purpose, but before enabling it consider: (1) Run the update commands with --dry-run first to confirm behavior (`clawdhub update --all --dry-run`). (2) Understand that global package updates may require sudo or change system-wide packages; ensure you have backups and can roll back if an update breaks things. (3) The update summary includes raw command output (errors, logs) — make sure the delivery target for summaries is a trusted channel. (4) Because updates fetch and install remote code (ClawdHub/registry and package managers), only enable automated updates if you trust the source registry and want automatic code changes applied. (5) If you prefer manual control, keep the cron job disabled and run updates manually.Like a lobster shell, security has layers — review code before you run it.
latestvk9756rpc4tcxrh46ff1zh8m37h83qw66
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔄 Clawdis
OSmacOS · Linux