How do I install the Auto Updater skill?

Run npx skillmds@latest add dvcrn/auto-updater-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Auto Updater safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Auto Updater?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Auto Updater free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Auto Updater?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Auto Updater by dvcrn — Agent Skill

Name: Auto Updater
Rating: 4.2 (5 reviews)
Author: dvcrn

Auto Updater

Set up and maintain automatic OpenClaw + skill updates on Windows/macOS/Linux. Use when a user asks for scheduled updates, manual update runs, update health checks, or update summaries. On Windows, enforce native Windows/Git Bash flow and avoid WSL bash paths.

dvcrn Updated Sep 9, 2026 32 repo stars

File contents

Auto-Updater Skill (Windows-first, cross-platform)

Configure safe recurring updates for OpenClaw and installed skills.

Core Rules

Prefer OpenClaw-native actions and npx clawhub.
On Windows, run updates in native Windows shell.
On Windows, ensure bash resolves to Git Bash / MSYS, not C:\Windows\System32\bash.exe (WSL launcher).
Never include user-specific local paths/usernames in public docs or published skill content.
Always output a concise summary: updated, unchanged, failed.

Windows-Only Guardrails (Important)

Do NOT use WSL for update execution.
If build steps require bash, prepend Git Bash path in PATH for the current shell session.
Verify active bash:

where.exe bash
bash --version

Expected on Windows: GNU bash from MSYS/Git, not WSL launcher path first.

Path Placeholders (Use These)

<openclaw-repo>: source repo root (example: %USERPROFILE%\\dev\\openclaw)
<openclaw-home>: runtime home (example: %USERPROFILE%\\.openclaw)

Manual Update Flow

1) Update OpenClaw (source install)

git -C <openclaw-repo> pull --ff-only
pnpm -C <openclaw-repo> install
pnpm -C <openclaw-repo> build

2) Restart gateway

Use OpenClaw gateway restart tool/action after successful build.

3) Update skills

npx clawhub update --all --workdir <openclaw-home> --no-input

If local edits exist and user confirms overwrite:

npx clawhub update <slug> --force --workdir <openclaw-home> --no-input

Successful Windows Command Template (Sanitized)

git -C <openclaw-repo> pull --ff-only
pnpm -C <openclaw-repo> install
pnpm -C <openclaw-repo> build
openclaw gateway restart
openclaw --version

Scheduling (Optional)

When user asks for automation, create cron jobs with isolated agentTurn runs and summary delivery. Keep schedule conservative (e.g., daily 04:00 local) unless user asks otherwise.

References

references/agent-guide.md
references/summary-examples.md

---name: auto-updater-4description: Set up and maintain automatic OpenClaw + skill updates on Windows/macOS/Linux. Use when a user asks for scheduled updates, manual update runs, update health checks, or update summaries. On Windows, enforce native Windows/Git Bash flow and avoid WSL bash paths.--- # Auto-Updater Skill (Windows-first, cross-platform) Configure safe recurring updates for OpenClaw and installed skills. ## Core Rules 1. Prefer OpenClaw-native actions and `npx clawhub`. 2. On **Windows**, run updates in **native Windows shell**. 3. On Windows, ensure `bash` resolves to **Git Bash / MSYS**, not `C:\Windows\System32\bash.exe` (WSL launcher). 4. Never include user-specific local paths/usernames in public docs or published skill content. 5. Always output a concise summary: updated, unchanged, failed. ## Windows-Only Guardrails (Important) - Do **NOT** use WSL for update execution. - If build steps require `bash`, prepend Git Bash path in PATH for the current shell session. - Verify active bash: ```powershell where.exe bash bash --version ``` Expected on Windows: GNU bash from MSYS/Git, **not** WSL launcher path first. ## Path Placeholders (Use These) - `<openclaw-repo>`: source repo root (example: `%USERPROFILE%\\dev\\openclaw`) - `<openclaw-home>`: runtime home (example: `%USERPROFILE%\\.openclaw`) ## Manual Update Flow ### 1) Update OpenClaw (source install) ```powershell git -C <openclaw-repo> pull --ff-only pnpm -C <openclaw-repo> install pnpm -C <openclaw-repo> build ``` ### 2) Restart gateway Use OpenClaw gateway restart tool/action after successful build. ### 3) Update skills ```powershell npx clawhub update --all --workdir <openclaw-home> --no-input ``` If local edits exist and user confirms overwrite: ```powershell npx clawhub update <slug> --force --workdir <openclaw-home> --no-input ``` ## Successful Windows Command Template (Sanitized) ```powershell git -C <openclaw-repo> pull --ff-only pnpm -C <openclaw-repo> install pnpm -C <openclaw-repo> build openclaw gateway restart openclaw --version ``` ## Scheduling (Optional) When user asks for automation, create cron jobs with isolated `agentTurn` runs and summary delivery. Keep schedule conservative (e.g., daily 04:00 local) unless user asks otherwise. ## References - `references/agent-guide.md` - `references/summary-examples.md`

Frequently asked questions