Skip to content
TrustedSkillsbeta
Back to all skills

Upgrade Guard

Unverified
jzOcb·v1.0.0·agents·MIT

Safe OpenClaw upgrades with snapshot, pre-flight checks, controlled upgrade steps, post-verification, and emergency rollback. Never lose your working system to a bad update again.

Repository

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $ openclaw skills install upgrade-guard

What we know about this skill

Publisher

jzOcb

Taken from the source listing. We haven't verified who controls this account.

Install target

Pinned to 564468d4

Installs fetch a stored snapshot of that commit, so the code can't change after the fact.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.telegram.org.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    127.0.0.1localapi.telegram.orgundeclared

    What it found

    • scripts/watchdog.sh:149contacts api.telegram.org
      "https://api.telegram.org/bot${token}/sendMessage" \

  • No credential access: failed

    Touches credential material in 1 place.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

    What it found

    • scripts/watchdog.sh:446browser cookie or password store
      rm -f "$user_data/Login Data"* 2>/dev/null

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jzocb/upgrade-guard at 564468d4b6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
564468d4b6
Manifest
SKILL.md
Scanned
6 files, 1,968 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The upgrade-guard skill protects OpenClaw installations from breaking during upgrades. It creates snapshots of the system before an upgrade, performs pre-flight checks for potential issues like plugin renames or dependency breaks, and provides a rollback mechanism if the upgrade fails. This prevents data loss and ensures continued operation even when unexpected problems arise.

When to use it

  • Before any OpenClaw version update: Run upgrade-guard before performing git pull && pnpm install.
  • When upgrading in production environments: The rollback feature is crucial for minimizing downtime during upgrades.
  • To proactively identify upgrade risks: Use the check command to surface potential issues before applying an upgrade.
  • After a failed upgrade attempt: Quickly revert to a known working state using the rollback command.

Key capabilities

  • System snapshotting (version, configuration, plugins, dependencies)
  • Pre-upgrade validation checks (disk space, git status, config validity)
  • Detection of plugin renames (e.g., clawdbot to openclaw)
  • Automated upgrade process with rollback on failure
  • Post-upgrade verification of key components (plugins, channels, models, gateway)

Example prompts

While this skill is primarily command-line driven, you might instruct an AI agent to:

  1. "Run the upgrade-guard snapshot command before I update OpenClaw."
  2. "Execute upgrade-guard check and report any potential upgrade issues."
  3. "If the upgrade-guard upgrade fails, run upgrade-guard rollback immediately."

Tips & gotchas

  • The skill relies on a clean Git repository before initiating an upgrade. Ensure all changes are committed or stashed beforehand.
  • Regularly review the output of the check command to understand potential upgrade risks and adjust configurations accordingly.