Auto Updater.Bak

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 instructions and requirements are consistent with its stated purpose (daily auto-updates for Clawdbot and installed skills); it is an instruction-only skill that sets up a cron job and helper script to run the expected update commands.

Purpose & Capability

Name/description (auto-update Clawdbot and skills) matches the instructions: uses clawdbot and clawdhub commands, heuristics for npm/pnpm/bun/source installs, and creates a cron job. There are no unrelated required binaries, env vars, or config paths declared.

Instruction Scope

SKILL.md and references direct the agent to create a helper script (~/.clawdbot/scripts/auto-update.sh), write logs to ~/.clawdbot/logs/, run global package manager updates (npm/pnpm/bun update -g), run 'clawdbot update' and 'clawdhub update --all', and register a Clawdbot cron job. These actions are within scope for an updater but will modify installed software and write files in the user's home directory; the instructions also suggest remedial commands (sudo, --force) which could elevate impact if used.

Install Mechanism

Instruction-only skill (no install spec, no archives/URLs). Nothing is downloaded or written by an installer beyond what the agent is explicitly told to create (script/log file). This minimizes install-time risk.

Credentials

The skill declares no required environment variables or credentials. It does, however, reference delivery options (e.g., '--provider telegram --to "@username"') and uses existing system tools (npm/pnpm/bun, git, clawdbot, clawdhub). If delivery/providers are configured elsewhere, update summaries may be sent externally; verify those provider tokens/configs before enabling automated runs.

Persistence & Privilege

The skill instructs creating a cron job and a persistent helper script and log file under the user's home (~/.clawdbot). It does not set always: true and does not modify other skills directly. Persistence is expected for an auto-updater, but this does grant ongoing automated ability to change installed software on the system under the user account.

Assessment

This skill appears to do what it says, but before enabling it consider: 1) Review the exact cron job command and the helper script it will create (~/.clawdbot/scripts/auto-update.sh) so you know what will run and when. 2) Run the update commands with --dry-run first (clawdhub update --all --dry-run) to see what would change. 3) Ensure you trust the ClawdHub registry and the source of installed skills—automatic updates can introduce breaking changes. 4) Check delivery/provider integrations (Telegram, email, etc.) to make sure summaries won't be sent to unintended external recipients. 5) Be mindful of permission requirements: global package updates may require elevated rights; avoid blindly following 'sudo' or '--force' suggestions without understanding consequences. 6) Keep backups or snapshots if you need a quick rollback strategy in case an update breaks critical workflows.

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