auto-updater-gateway

What This Skill Does

The auto-updater-gateway skill provides a robust, automated framework for maintaining the health and currency of your Clawdbot environment and installed skills. Rather than relying on manual intervention, this skill leverages the Clawdbot Gateway cron scheduler to execute periodic maintenance routines. It performs a comprehensive suite of actions, including checking for ClawHub skill updates, optionally applying core Clawdbot updates, triggering system restarts when necessary, and running diagnostic checks via clawdbot doctor. By centralizing these tasks, it ensures that your environment remains patched, consistent, and error-free without manual oversight.

Installation

To integrate this workflow into your system, use the following CLI command. Ensure you have authenticated your session via clawdhub login before proceeding:

clawhub install openclaw/skills/skills/xabo1986/auto-updater-gateway

After installation, you must configure your scheduling parameters. The skill is designed to run as an isolated job to prevent context pollution in your primary terminal. Use the clawdbot cron add command to define your desired schedule, ensuring you set the --tz flag to match your local timezone to avoid off-hour execution.

Use Cases

• Automated Skill Maintenance: Keeping all plugins and hub-managed modules updated to their latest versions daily.
• Overnight System Health Checks: Running clawdbot doctor during off-peak hours to identify and log potential configuration drift or runtime issues.
• Reliable Reporting: Receiving automated status summaries via Telegram to verify that updates were applied correctly and that the system remains stable after potential restarts.
• Zero-Touch Lifecycle Management: Perfect for headless setups or server-based instances where accessing the CLI to run updates manually is inconvenient.

Example Prompts

1. "Schedule a daily update for Clawdbot and all skills at 3:00 AM Europe/Stockholm and send the summary report to my Telegram ID 2095290688."
2. "Set up an isolated cron job that runs a doctor check and updates all skills every Sunday at midnight, and notify me if any errors occur."
3. "Please configure the auto-updater to include core Clawdbot updates and trigger a system restart if a new version is detected during the 4 AM routine."

Tips & Limitations

• Permissions: Ensure the user running the cron job has sufficient permissions to restart the Clawdbot process and execute clawdhub commands.
• Isolated Sessions: Always use --session isolated to ensure that your primary user environment is not interrupted by update-related output.
• Disruption: Core Clawdbot updates require a restart. Schedule these during downtime to avoid terminating active tasks unexpectedly.
• Troubleshooting: If the updater reports 'Not logged in', verify your environment variables and re-run the clawdhub login command in the Gateway execution context.