About this skill

Problem

When maintaining multiple OpenClaw skills, manual updates can miss versions, obscure the source, and make failures hard to diagnose. Without backups and reports, rollback becomes manual and noisy; if night-time updates send immediate notifications, they disrupt the morning workflow.

How It Works

Dual-source updates: processes skills one by one, tries the original configured source first, then falls back to skillhub if the first attempt fails.
Pre-update backup: copies the current skill to ~/.openclaw/workspace/skills/.backups/ before replacing it, preserving a rollback path.
Detailed reporting: records the update source, success or failure, version changes, and feature notes from CHANGELOG.md or SKILL.md.
Silent window plus digest delivery: updates during 1:00–6:00 are not pushed immediately; results are bundled into the morning digest after 07:00.
Flexible scheduling: the update run time and digest push time are controlled separately through crontab, with common defaults of 04:00 and 08:00.
Reports are written to .auto-update-note.txt for digest integration and AUTO_UPDATE_LOG.md for history.

Boundaries

Best for OpenClaw setups that prefer scheduled overnight updates and one morning summary.
Not ideal when every update must trigger an instant alert, or when the workflow should not depend on crontab and a morning digest script.
It fetches only from the original source or skillhub; fallback success still depends on the availability and content of the backup source.

Screenshots

Use Cases

Run overnight OpenClaw skill updates and review the consolidated morning digest.
Back up skills before updates and roll back manually from the backup directory if a release fails.
Diagnose a failed skill update by inspecting AUTO_UPDATE_LOG.md history.
Integrate update-report reading into a morning digest script so push notices include version changes.

Best For

Engineers maintaining multiple OpenClaw skills who want quiet overnight updates and a consolidated morning report.
Automation owners running digest scripts who need skill update results included in morning notices.
Maintainers debugging failed updates or source fallback who need logs and backup rollback paths.
Agent operations staff managing schedules who require silent updates and time-controlled push delivery.