Auto-Updater

Problem to Solve

When Clawdbot and multiple skills run under a long-lived Gateway setup, version drift becomes routine: the main runtime needs migrations, skills may receive new registry versions, and package dependencies can conflict. With several skills installed, manually checking clawdbot doctor, clawdhub update --all, and each local version is time-consuming and easy to forget. @zcwl/auto-updater consolidates this into a daily scheduled task that checks for updates, applies them, and posts the result back to the main session.

How It Works

The skill configures a daily cron job, defaulting to 4:00 AM, with time and timezone adjustable via --cron and --tz. The main steps are:

• Update Clawdbot itself: npm/pnpm/bun installs are updated through package managers; git checkout installs pull updates; clawdbot doctor runs afterward to apply migrations.
• Update installed skills: clawdhub update --all compares local skills against the registry and updates available versions.
• Produce an update summary: after completion, a message is sent to the main session listing what changed and why failures happened; failure notes point to permission, network, or package conflict diagnostics.

Boundaries

This skill fits continuously running Gateway environments where cron is enabled. If cron is disabled, the Gateway is not running continuously, or the user lacks write permission to skill directories, updates may not run or may fail. It does not handle application release, rollback, dependency lock repair, or manual validation of critical changes; in high-risk environments, review versions and update diffs manually before applying them automatically.