Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Safely update OpenClaw with pre-flight checks and rollback support. Use when updating OpenClaw, checking for updates, or recovering from a failed update. Han...
Safely update OpenClaw with pre-flight checks and rollback support. Use when updating OpenClaw, checking for updates, or recovering from a failed update. Han...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Safely update OpenClaw with automatic pre-flight safety checks and rollback capability.
Before running openclaw update, always run the pre-update script: bash scripts/pre-update.sh Optional: specify a backup script to run during pre-flight: BACKUP_SCRIPT=~/repo/scripts/backup-openclaw.sh bash scripts/pre-update.sh The script will: Find all workspace* directories under ~/.openclaw/ Git commit any uncommitted changes (init git if missing) Back up openclaw.json to /tmp/openclaw.json.bak Run the backup script if provided Save the current version to /tmp/openclaw-prev-version.txt
The update script sends success/failure notifications via Telegram Bot API (bypasses OpenClaw gateway, so it works even if the update breaks the gateway). Create ~/.openclaw/.telegram-notify.env: TELEGRAM_BOT_TOKEN=<your-bot-token> TELEGRAM_CHAT_ID=<your-chat-id> chmod 600 ~/.openclaw/.telegram-notify.env The bot token is the same one used by your OpenClaw Telegram channel. Chat ID can be found via openclaw directory.
Run the full update with automatic pre-flight + notification: bash scripts/update.sh This will: pre-flight → update → wait for gateway → notify via Telegram.
After pre-flight passes: openclaw update
After updating, verify: openclaw status openclaw gateway status Check that: Version shows the new release Gateway is running All agents are responsive
If the update breaks something: bash scripts/rollback.sh The script will: Read the saved previous version from /tmp/openclaw-prev-version.txt Install that version via npm install -g openclaw@<version> Optionally restore openclaw.json from backup Restart the gateway
If the rollback script isn't available: # Install specific version npm install -g openclaw@<version> # Restore config cp /tmp/openclaw.json.bak ~/.openclaw/openclaw.json # Restart openclaw gateway restart
If config and workspaces are both corrupted: # Find latest backup ls -t ~/repo/backups/openclaw-*.tar.gz | head -1 # Restore (overwrites ~/.openclaw/) tar xzf ~/repo/backups/openclaw-<timestamp>.tar.gz -C ~/
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.