My Auto Updater

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 requests and instructions are consistent with an auto-updater for Clawdbot and installed skills; nothing requested or instructed is disproportionate to that purpose.

Purpose & Capability

Name and description match the actions in SKILL.md: adding a cron job, running Clawdbot/package-manager commands, and running clawdhub to update skills. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

Instructions tell the agent to run update commands, create an optional helper script in the user's home (~/.clawdbot/scripts/auto-update.sh), log to ~/.clawdbot/logs/auto-update.log, and emit a simple update summary for the agent to parse. These actions are in-scope for an auto-updater, but they will perform writes to the user's home and execute package-manager commands that modify system state (including global npm/pnpm/bun updates and running 'clawdbot doctor').

Install Mechanism

Instruction-only skill with no install spec or downloaded code. No archive downloads or external install URLs. This is a low-risk install surface from a packaging/install perspective.

Credentials

The skill declares no required env vars, credentials, or config paths. The SKILL.md uses standard local paths under the user's home and only references commands (clawdbot, clawdhub, npm/pnpm/bun) relevant to the stated task.

Persistence & Privilege

always is false and the skill is user-invocable (normal). The skill recommends creating a cron job (persistent behavior) and suggests using an 'isolated' session. Because it updates installed skills automatically, granting it scheduled execution does carry supply-chain risk (it will accept and install new skill versions from the registry if available).

Assessment

This skill is internally coherent for auto-updating Clawdbot and installed skills, but take care before enabling automatic updates: - Supply-chain risk: automatic updates will install new versions of skills from the registry. Only enable this if you trust the registry and the maintainers of installed skills. Consider running 'clawdhub update --all --dry-run' first. - Permissions: global package updates may require elevated permissions; avoid running scheduled updates as root. Fix directory ownerships instead of granting broad sudo where possible. - Use isolation and review logs: prefer the recommended 'isolated' session, and review ~/.clawdbot/logs/auto-update.log and the update summary after runs. - Consider staged rollout: start with dry-run or weekly updates, or restrict to a curated list of skills rather than --all, if you rely on specific skills for critical workflows. - Backups and recovery: ensure you have a way to roll back or reinstall if an update causes breakage; keep a snapshot of important configurations. If you want extra safety, ask the agent to perform only the dry-run and produce the update summary for your manual approval before applying updates.

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