Clawdbot Release Check

jdrhyne/clawdbot-release-check

Check for new OpenClaw releases and notify once per new version.

3k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

239

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/jdrhyne/agent-skills --skill clawdbot-release-check

The instruction itself

6 sections, as written by the author

OpenClaw Release Check

Checks for new OpenClaw releases from GitHub and notifies once per version (no spam).

Installation

clawhub install clawdbot-release-check

Quick Setup (cron)

# Add daily update check at 9am, notify via Telegram
{baseDir}/scripts/setup.sh --telegram YOUR_TELEGRAM_ID

# Custom hour
{baseDir}/scripts/setup.sh --hour 8 --telegram YOUR_TELEGRAM_ID

# Remove cron job
{baseDir}/scripts/setup.sh --uninstall

After setup, restart gateway:

openclaw gateway restart

Manual Usage

{baseDir}/scripts/check.sh
{baseDir}/scripts/check.sh --status
{baseDir}/scripts/check.sh --force
{baseDir}/scripts/check.sh --all-highlights
{baseDir}/scripts/check.sh --reset
{baseDir}/scripts/check.sh --help

Files

State: ~/.openclaw/clawdbot-release-check-state.json
Cache: ~/.openclaw/clawdbot-release-check-cache.json

Configuration

Environment variables:

OPENCLAW_DIR — path to OpenClaw source/install
CACHE_MAX_AGE_HOURS — cache TTL in hours (default: 24)

How to use it

Copy the folder

Take jdrhyne/clawdbot-release-check from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.