Auto-Updater (Gateway)

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.

Security Scan

The skill is an instruction-only workflow for scheduling Clawdbot/skill updates via the Gateway cron scheduler and its requirements and instructions are coherent with that purpose.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md explains setting up Gateway cron jobs that run clawdhub update --all and optionally clawdbot self-updates. The declared binary requirement (either clawdbot or clawdhub) is appropriate and proportionate.

Instruction Scope

Instructions stay within the updater automation scope. They include concrete example commands (including absolute example paths and a sample Telegram recipient ID). Be aware that the job's delivery options (channel + to) will transmit update summaries to whatever external endpoint you configure, which could disclose installed-skill/version info if sent to an untrusted recipient. The SKILL.md does not instruct reading unrelated system files or exfiltrating secrets, but users copying example absolute paths verbatim may unintentionally reference another user's filesystem/layout.

Install Mechanism

No install spec and no code files — instruction-only; nothing will be written to disk by the skill itself. This is the lowest-risk install posture.

Credentials

The skill declares no environment variables or credentials, which is consistent with its role as a config/workflow recipe. Note: runtime actions (clawdhub login, creating Gateway jobs that deliver to Telegram) do rely on existing logged-in accounts and delivery channel configuration outside the skill; that is expected but should be handled by the user/agent according to normal credential practices.

Persistence & Privilege

always:false and default invocation settings — the skill does not request permanent/always-on inclusion or elevated platform-wide privileges. It also does not modify other skills' configurations.

Assessment

This skill is a coherent how-to for scheduling automatic updates; it's not trying to hide unrelated access. Before installing or copying the example: 1) Verify clawdbot and clawdhub are the correct binaries on your system (don't blindly copy the example absolute paths). 2) Test with report-only mode first (do not enable self-update/restart) to confirm behavior. 3) Ensure the delivery channel/recipient you configure is trusted — update reports include version lists and could reveal internal state. 4) Be prepared for potential downtime if you enable Clawdbot self-updates and automatic restarts. If you need higher assurance, ask the skill author for a generic example (no user-specific paths/IDs) or for explicit checks the job will run before restarting services.

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

2. 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)

2. Update skills

• clawdhub update --all

3. (Optional) Update Clawdbot

• Only if the owner explicitly wants self-updates.
• After updating, run clawdbot doctor --non-interactive.
• Restart gateway if required.

4. 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.