Auto Updater Backup

Automatically 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...

Security Scan

The skill's requested actions, files, and instructions match its stated purpose (daily auto-updates of Clawdbot and installed skills) and do not ask for disproportionate credentials or unrelated system access.

Purpose & 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.

Auto-Updater Skill

Keep your Clawdbot and skills up to date automatically with daily update checks.

What It Does

This skill sets up a daily cron job that:

1. Updates Clawdbot itself (via clawdbot doctor or package manager)
2. Updates all installed skills (via clawdhub update --all)
3. Messages you with a summary of what was updated

Setup

Quick Start

Ask Clawdbot to set up the auto-updater:

Set up daily auto-updates for yourself and all your skills.

Or manually add the cron job:

clawdbot cron add \
  --name "Daily Auto-Update" \
  --cron "0 4 * * *" \
  --tz "America/Los_Angeles" \
  --session isolated \
  --wake now \
  --deliver \
  --message "Run daily auto-updates: check for Clawdbot updates and update all skills. Report what was updated."

Configuration Options

Option	Default	Description
Time	4:00 AM	When to run updates (use --cron to change)
Timezone	System default	Set with --tz
Delivery	Main session	Where to send the update summary

How Updates Work

Clawdbot Updates

For npm/pnpm/bun installs:

npm update -g clawdbot@latest
# or: pnpm update -g clawdbot@latest
# or: bun update -g clawdbot@latest

For source installs (git checkout):

clawdbot update

Always run clawdbot doctor after updating to apply migrations.

Skill Updates

clawdhub update --all

This checks all installed skills against the registry and updates any with new versions available.

Update Summary Format

After updates complete, you'll receive a message like:

🔄 Daily Auto-Update Complete

**Clawdbot**: Updated to v2026.1.10 (was v2026.1.9)

**Skills Updated (3)**:
- prd: 2.0.3 → 2.0.4
- browser: 1.2.0 → 1.2.1  
- nano-banana-pro: 3.1.0 → 3.1.2

**Skills Already Current (5)**:
gemini, sag, things-mac, himalaya, peekaboo

No issues encountered.

Manual Commands

Check for updates without applying:

clawdhub update --all --dry-run

View current skill versions:

clawdhub list

Check Clawdbot version:

clawdbot --version

Troubleshooting

Updates Not Running

1. Verify cron is enabled: check cron.enabled in config
2. Confirm Gateway is running continuously
3. Check cron job exists: clawdbot cron list

Update Failures

If an update fails, the summary will include the error. Common fixes:

• Permission errors: Ensure the Gateway user can write to skill directories
• Network errors: Check internet connectivity
• Package conflicts: Run clawdbot doctor to diagnose

Disabling Auto-Updates

Remove the cron job:

clawdbot cron remove "Daily Auto-Update"

Or disable temporarily in config:

{
  "cron": {
    "enabled": false
  }
}

Resources

• Clawdbot Updating Guide
• ClawdHub CLI
• Cron Jobs