agentleFS
Sign inStart free
weininghuiweininghui/skills/auto-updater/SKILL.md

auto-updater

Skill1 starsChanged 12 days agoMITView on GitHub

Schedule and run safe daily/weekly updates for Clawdbot + installed skills using the Gateway cron scheduler. Use when setting up \"run updates at 04:00\" jobs, rotating update reports, running `clawdhub update --all`, and (optionally) applying Clawdbot updates + restart + doctor.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a reliable daily auto-update routine using Clawdbot Cron (Gateway scheduler).

    line 10
  2. Distinctive:

    Ensure ClawHub CLI is logged in (for skill updates):

    line 16
  3. Distinctive:

    When to run (cron + timezone)

    line 24
  4. Distinctive:

    Use an isolated cron job so it doesn’t spam the main session context.

    line 29
  5. Distinctive:

    Only if the owner explicitly wants self-updates.

    line 58
  6. Very specific:

    After updating, run clawdbot doctor --non-interactive.

    line 59
  7. Very specific:

    Delivery: Prefer explicit channel + to so the job always reaches you.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

迁移说明:本技能原为 OpenClaw / ClawHub 生态技能,现已转为 WorkBuddy 技能规范。正文如出现 openclaw / clawhub / claw 命令或 ~/.openclaw 路径,请忽略该命令形式,改用 WorkBuddy 等价操作:技能目录 = ~/.workbuddy/skills/<name>/;装包用 pip / npm;联网用 WebSearch / WebFetch;读写文件用 Read / Write / Edit;执行命令用 Bash(Windows 走 PowerShell 工具)。

Auto-Updater (Gateway)

Create a reliable daily auto-update routine using Clawdbot Cron (Gateway scheduler).

This is a "skill" in the sense of a repeatable workflow + correct config shapes (not a plugin).

Quick setup checklist

  1. Ensure ClawHub CLI is logged in (for skill updates):
/home/xabo/.nvm/versions/node/v22.22.0/bin/clawdhub login --workdir /home/xabo/clawd --dir skills
/home/xabo/.nvm/versions/node/v22.22.0/bin/clawdhub whoami --workdir /home/xabo/clawd --dir skills
  1. Decide:
  • When to run (cron + timezone)
  • Whether the job should only report, or update + restart

Recommended cron job (isolated, deliver output)

Use an isolated cron job so it doesn’t spam the main session context.

Example CLI (04:00 Europe/Stockholm):

/home/xabo/.nvm/versions/node/v22.22.0/bin/clawdbot cron add \
  --name "Daily auto-update (Clawdbot + skills)" \
  --cron "0 4 * * *" \
  --tz "Europe/Stockholm" \
  --session isolated \
  --wake now \
  --deliver \
  --channel telegram \
  --to "2095290688" \
  --message "Run daily auto-update: update skills via clawdhub update --all; if Clawdbot has an update available, apply it and restart; then run clawdbot doctor --non-interactive; report what changed."

What the job should do (workflow)

Within the cron run:

  1. Capture “before” state
  • clawdbot --version
  • clawdhub list (skills + versions)
  1. Update skills
  • clawdhub update --all
  1. (Optional) Update Clawdbot
  • Only if the owner explicitly wants self-updates.
  • After updating, run clawdbot doctor --non-interactive.
  • Restart gateway if required.
  1. Send a concise summary
  • Clawdbot version before/after
  • Skills updated (old → new)
  • Any errors

Notes / gotchas

  • Timezone field: in Gateway job objects this is schedule.tz (IANA tz like Europe/Stockholm).
  • Delivery: Prefer explicit channel + to so the job always reaches you.
  • Clawdbot self-update: can be disruptive (restarts). Run at a quiet time.

Troubleshooting

  • clawdhub update says “Not logged in” → run clawdhub login again.
  • Job doesn’t run → confirm Gateway is always-on and cron is enabled.
  • Nothing updates → that can be normal; still send a “no changes” report.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free