Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Release Tracker
Track GitHub repository releases and generate prioritized summaries. Supports multiple repos, custom priority keywords, and delivery to Discord (forum posts...
skill openclawclawhub Free
Track GitHub repository releases and generate prioritized summaries. Supports multiple repos, custom priority keywords, and delivery to Discord (forum posts...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/config-examples.md, scripts/setup.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.1.0
Provenance
- Publisher
- jo9900
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Release Tracker
Monitor one or more GitHub repositories for new releases, generate prioritized summaries, and deliver them to configured channels.
Prerequisites
gh CLI installed and authenticated (gh auth status) For Discord delivery: Discord channel configured in OpenClaw
Single Repo Setup
Set up tracking for one repo with a cron job: 1. Create a config file at <workspace>/release-tracker.json (see Configuration) 2. Create a cron job (isolated, daily) that runs the check 3. The cron reads config, checks GitHub, compares versions, posts if new
Multi-Repo Setup
Add multiple repos to the repos array in config. Each repo has independent version tracking and priority rules.
Configuration
Store config at <workspace>/release-tracker.json: { "repos": [ { "owner": "openclaw", "repo": "openclaw", "displayName": "OpenClaw", "priorities": ["discord", "voice", "telegram", "cron", "agent"], "outputChannel": "<your-discord-channel-id>", "outputFormat": "discord-forum", "language": "en", "includePrerelease": false } ], "versionStore": "release-tracker-state.json", "schedule": "0 10 * * *", "timezone": "UTC" }
Config Fields
repos[].owner / repos[].repo โ GitHub owner/repo repos[].displayName โ friendly name for output header repos[].priorities โ keywords to sort higher in summary (matched against changelog text) repos[].outputChannel โ Discord channel/forum ID for delivery repos[].outputFormat โ discord-forum | discord-channel | telegram | slack | text discord-forum: create a new forum post per release discord-channel: send a message to a Discord channel telegram: send a message to a Telegram chat/channel/group slack: send a message to a Slack channel text: return plain text (for piping to other tools) repos[].language โ zh | en (summary language) repos[].includePrerelease โ track pre-release/RC versions repos[].filter โ optional, stable | all (default: stable) versionStore โ filename for tracking last-seen versions (relative to workspace) schedule โ cron expression for check frequency timezone โ timezone for cron schedule
Check for New Releases
Read config from release-tracker.json Read version state from <versionStore> For each repo: gh release list --repo <owner>/<repo> --limit 5 --json tagName,publishedAt,isPrerelease Compare latest tag against stored version If new version found, proceed to summarize
Generate Summary
Fetch release content: gh release view <tag> --repo <owner>/<repo> --json body If release body is sparse, also check local CHANGELOG if the package is installed: cat /opt/homebrew/lib/node_modules/<package>/CHANGELOG.md Parse and categorize changes into sections: Priority items โ lines matching any priorities keywords, shown first Features โ new capabilities Breaking changes โ marked with โ ๏ธ Fixes โ bug fixes relevant to user (skip internal/CI fixes) Security โ collapsed at bottom unless critical Skip: CI/test-only changes, dependency bumps, internal refactors
Prioritization Rules
Sort entries within each section: Lines matching priorities keywords โ top User-facing changes โ middle Internal/infrastructure โ bottom Omit: trivial fixes, test-only changes, doc typos
Format Output
Discord Forum (discord-forum) Title: ๐ฆ v{version} Body: ## {displayName} v{version} ### โญ Key Features {priority matches + features, formatted as bold headers with descriptions} ### โ ๏ธ Breaking Changes {breaking changes with migration notes} ### ๐ง Fixes {relevant fixes, grouped by area} ### ๐ก๏ธ Security {security fixes, brief} Discord Channel (discord-channel) Compact single-message format, max 2000 chars. Telegram (telegram) Same structure as Discord Channel but respects Telegram formatting (markdown v2). Max 4096 chars. Slack (slack) Same structure, uses Slack mrkdwn formatting. Max 3000 chars. Text (text) Plain markdown, no emoji headers.
Deliver
Based on outputFormat: discord-forum: message(action=thread-create, channelId=<outputChannel>, threadName=<title>, message=<body>) discord-channel: message(action=send, channel=discord, target=<outputChannel>, message=<body>) telegram: message(action=send, channel=telegram, target=<outputChannel>, message=<body>) slack: message(action=send, channel=slack, target=<outputChannel>, message=<body>) text: return as tool result
Update State
After successful delivery, update version store: { "openclaw/openclaw": { "lastVersion": "2026.2.22-2", "lastCheckedAt": "2026-02-24T10:00:00+09:00", "lastPublishedAt": "2026-02-22T..." } }
Cron Setup
Create the cron job for automated checking: Name: release-tracker Schedule: {config.schedule} with tz {config.timezone} Session: isolated Payload: agentTurn with message referencing this skill Delivery: none (skill handles its own delivery) The cron message should instruct the agent to: Read release-tracker.json for config Read release-tracker-state.json for last versions Check each repo via gh release list If new releases found, generate summaries and deliver Update state file
Manual Check
User can trigger manually: "check for new releases" or "any updates on openclaw?" The agent should: Load config Run the check workflow Report findings conversationally (not necessarily in forum format)
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs1 Scripts
- SKILL.md
- references/config-examples.md
- scripts/setup.sh