Skip to main content
skill CX Codex

clawdbot-release-check — Claude Code skill: what it does

clawdbot-release-check watches GitHub for new OpenClaw releases and pings you once per version. Can run on a cron schedule and send the notice to Telegram.

MIT ★ 239 updated 2026-08-30

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jdrhyne/agent-skills --skill clawdbot-release-check -a claude-code
Open on GitHub

What clawdbot-release-check does

The skill polls OpenClaw's GitHub releases and reports a new version a single time. Seen versions are recorded in ~/.openclaw/clawdbot-release-check-state.json, so the same release does not come back. A cache sits beside it at ~/.openclaw/clawdbot-release-check-cache.json; CACHE_MAX_AGE_HOURS sets how long entries live, 24 by default.

Two scripts carry the work. scripts/setup.sh writes a cron job for the hour you pass (--hour 8) and can hook up Telegram alerts for your ID, while --uninstall takes the job out again. scripts/check.sh runs a check on demand: --status lists what has been marked, --force skips the cache, --reset wipes the history.

You need curl and jq on the machine, otherwise there is nothing to run the check with. OPENCLAW_DIR points at the OpenClaw source or install. After the cron setup the gateway gets restarted with openclaw gateway restart.

What it helps with

  • learn about an OpenClaw release without browsing GitHub
  • get one alert per version instead of repeats
  • schedule a daily release check with cron
  • send release notices to Telegram
  • clear the seen-versions history and start over

Example prompts for the agent

  • Set up the daily check for 8am and send alerts to my Telegram: {baseDir}/scripts/setup.sh --hour 8 --telegram YOUR_TELEGRAM_ID
  • Run the check right now and ignore the cache: {baseDir}/scripts/check.sh --force
  • Show which versions are already marked as seen with {baseDir}/scripts/check.sh --status

How to install clawdbot-release-check

1Skills CLI (Vercel)

npx skills add jdrhyne/agent-skills --skill clawdbot-release-check -a claude-code

2Manually: put the files in place

~/.claude/skills/clawdbot-release-check/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/clawdbot-release-check/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about clawdbot-release-check

How do I install clawdbot-release-check in Claude Code?

Run npx skills add jdrhyne/agent-skills --skill clawdbot-release-check -a claude-code. The skill file lands at ~/.claude/skills/clawdbot-release-check/SKILL.md.

What does clawdbot-release-check do?

It checks GitHub for new OpenClaw releases and notifies you once per version, either on a schedule or when you run it by hand.

What does the skill need to run?

curl and jq must be available. OPENCLAW_DIR tells it where OpenClaw lives.

Source text

SKILL.md · MIT
---
name: clawdbot-release-check
description: Check for new OpenClaw releases and notify once per new version.
homepage: https://github.com/openclaw/openclaw
metadata: {"openclaw":{"emoji":"🔄","requires":{"bins":["curl","jq"]}}}
---

# OpenClaw Release Check

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

## Installation

```bash
clawhub install clawdbot-release-check
```

## Quick Setup (cron)

```bash
# 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:

```bash
openclaw gateway restart
```

## Manual Usage

```bash
{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)

© jdrhyne · MIT · jdrhyne/agent-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set27

The whole set →
last30days last30days researches conversations from the past month across Reddit, X, and the web, returning synthesized summaries and ready-to-use prompts. CX Codex +1 ★ 239repo stars clawddocs Find OpenClaw guidance, configuration examples, and recently changed docs with clawddocs. Use it while setting up a provider, troubleshooting, or deploying OpenClaw. CX Codex +1 ★ 239repo stars auto-updater auto-updater configures daily cron tasks to upgrade OpenClaw and installed ClawHub skills, sending a summary message with all applied changes. CX Codex +1 ★ 239repo stars skill-sync skill-sync is a Claude Code skill that keeps local skills in sync with a shared GitHub repository by listing skills, installing updates, and submitting local changes through pull requests. CX Codex +1 ★ 239repo stars Zendesk Work with Zendesk tickets and users through the API, or export queue data on request. Configure the required environment variables before connecting. CX Codex +1 ★ 239repo stars knowledge-graph The knowledge-graph skill keeps durable facts about people, companies, and projects in a workspace graph. Use it to carry useful context between sessions and look it up without reopening long transcripts. CX Codex +1 ★ 239repo stars self-improving-agent self-improving-agent keeps a small journal in .learnings/ with failures, user corrections and missing-capability requests, then reads it back before big jobs. CX Codex +1 ★ 239repo stars planner planner structures complex projects into sprints and atomic tasks with acceptance criteria, preparing ready-to-run plans for subagents. CX Codex +1 ★ 239repo stars

Project sponsors

Companies that keep this analytics open