Skip to content
Back to skills

Clawdbot Release Check

ASecurity

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

  • 651 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 10, 2026
documentationbashgitapi

Works with

  • api

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro scans all 3 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add sundial-org/awesome-openclaw-skills --skill clawdbot-release-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Clawdbot Release Check?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Clawdbot Release Check
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/sundial-org-clawdbot-release-check/badge)](https://www.skillsdirectory.com/skills/sundial-org-clawdbot-release-check)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: clawdbot-release-check
description: Check for new clawdbot releases and notify once per new version.
homepage: https://github.com/clawdbot/clawdbot
metadata: {"clawdbot":{"emoji":"πŸ”„","requires":{"bins":["curl","jq"]}}}
---

# Clawdbot Release Check

Checks for new clawdbot releases from GitHub and notifies you once per version. No nagging.

## Installation

```bash
clawdhub install clawdbot-release-check
```

## Quick Setup (with cron)

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

# Custom hour (e.g., 8am)
{baseDir}/scripts/setup.sh --hour 8 --telegram YOUR_TELEGRAM_ID

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

After setup, restart the gateway:
```bash
launchctl kickstart -k gui/$(id -u)/com.clawdis.gateway
```

## Manual Usage

```bash
# Check for updates (silent if up-to-date or already notified)
{baseDir}/scripts/check.sh

# Show version info
{baseDir}/scripts/check.sh --status

# Force notification (bypass "already notified" state)
{baseDir}/scripts/check.sh --force

# Show highlights from ALL missed releases
{baseDir}/scripts/check.sh --all-highlights

# Clear state (will notify again on next check)
{baseDir}/scripts/check.sh --reset

# Help
{baseDir}/scripts/check.sh --help
```

## How It Works

1. Fetches latest release from `github.com/clawdbot/clawdbot/releases`
2. Compares with your installed version (from `package.json`)
3. If behind, shows highlights from release notes
4. Saves state to prevent repeat notifications

## Example Output

```
πŸ”„ **Clawdbot Update Available!**

Current: `2.0.0-beta5`
Latest:  `2026.1.5-3`

_(3 versions behind)_

**Highlights:**
- Models: add image-specific model config
- Agent tools: new `image` tool
- Config: default model shorthands

πŸ”— https://github.com/clawdbot/clawdbot/releases/tag/v2026.1.5-3

To update: `cd /path/to/clawdis && git pull && pnpm install && pnpm build`
```

## Files

**State** β€” `~/.clawdbot/clawdbot-release-check-state.json`:
```json
{
  "lastNotifiedVersion": "v2026.1.5-3",
  "lastCheckMs": 1704567890123
}
```

**Cache** β€” `~/.clawdbot/clawdbot-release-check-cache.json`:
- Release data cached for 24 hours (saves API calls)
- Highlights extracted once per release (saves tokens)
- Use `--clear-cache` to force refresh

## Configuration

Environment variables:
- `CLAWDBOT_DIR` β€” Path to clawdbot source (auto-detected from `~/dev/clawdis`, `~/clawdbot`, or npm global)
- `CACHE_MAX_AGE_HOURS` β€” Cache TTL in hours (default: 24)


Files in this skill

  • SKILL.md2.5 KB
  • scripts/check.sh7.5 KB
  • scripts/setup.sh3.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…