Auto Updater 1.0.0
Scanned@pntrivedy
npx machina-cli add skill @pntrivedy/auto-updater-1-0-0 --openclawAuto-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:
- Updates Clawdbot itself (via
clawdbot doctoror package manager) - Updates all installed skills (via
clawdhub update --all) - 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
- Verify cron is enabled: check
cron.enabledin config - Confirm Gateway is running continuously
- 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 doctorto diagnose
Disabling Auto-Updates
Remove the cron job:
clawdbot cron remove "Daily Auto-Update"
Or disable temporarily in config:
{
"cron": {
"enabled": false
}
}
Resources
Overview
Auto-Updater sets up a daily cron job to check for and apply updates to Clawdbot and all installed skills, then sends a summary of changes. This helps keep your bot ecosystem current without manual intervention.
How This Skill Works
A daily cron entry is created (default 4:00 AM in America/Los_Angeles) to run updates. It updates Clawdbot (via npm/pnpm/bun global update or clawdbot update for source installs), updates all installed skills (clawdhub update --all), and delivers a summary message. After updates, you should run clawdbot doctor to apply migrations.
When to Use It
- You want automatic, daily updates for Clawdbot and every installed skill without manual checks.
- You manage multiple skills and want centralized updates triggered on a schedule.
- You rely on cron-based maintenance and prefer hands-off upkeep.
- You want a readable, delivered summary showing exactly what changed after updates.
- You need to verify post-update migrations and version changes promptly.
Quick Start
- Step 1: Ask Clawdbot to set up daily auto-updates for yourself and all your skills.
- Step 2: Or manually add the cron using: 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."
- Step 3: Verify the cron is configured and observe the delivery of the update summary after each run.
Best Practices
- Ensure cron is enabled and the default or configured time (cron and tz) matches your environment.
- Confirm Gateway is running continuously so cron tasks execute reliably.
- Check for the cron job with clawdbot cron list to verify it exists.
- Use clawdhub update --all --dry-run to preview updates before applying.
- After updates, run clawdbot doctor to apply migrations and maintain consistency.
Example Use Cases
- Daily Auto-Update completes: Clawdbot updated to v2026.2.0 and 3 skills updated; summary delivered.
- Daily Auto-Update runs but only skills updated; Clawdbot remained at the same version; summary lists updated skills.
- All skills already current: summary shows Skills Already Current (5) and no changes.
- Dry-run shows pending updates without applying; user reviews changes before proceeding.
- Auto-updates disabled temporarily by removing the cron job; a manual update can be run instead.
