repo-update-check

Compares installed versions of Hermes, QWEN-gate, 9router, and mem0 against upstream stable releases.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/SillyHippy/zo-skills --skill repo-update-check-sillyhippy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-update-check
Source: https://github.com/SillyHippy/zo-skills/tree/main/skills/repo-update-check
Command: npx skills add https://github.com/SillyHippy/zo-skills --skill repo-update-check-sillyhippy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually tracking whether locally installed tools like Hermes, QWEN-gate, 9router, and mem0 are behind their upstream releases is error-prone and easy to forget. This Skill replaces LLM guessing with a deterministic script that checks installed versions against GitHub and PyPI releases and reports only stable updates. ## Core Features & Use Cases - Deterministic Version Comparison: Reads installed versions via git describe and pip, then compares them against the latest GitHub releases and PyPI versions using semantic version parsing. - Stable-Release Filtering: Ignores nightly, alpha, beta, rc, pre, and dev tags so notifications only fire for stable upstream releases. - Telegram Notification Gating: Outputs JSON with should_notify and a ready-to-send telegram_message, so daily automations only message when a stable update exists. - Use Case: A daily Zo Computer automation runs the script each morning; when mem0ai publishes a new stable PyPI release, the user receives a Telegram message listing the installed and upstream versions, with no unattended upgrades applied. ## Quick Start Run the repo update check script and send me a Telegram message only if it reports that a stable update is available.

Frequently Asked Questions about repo-update-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if installed GitHub repos are behind the latest release?▼

Run the check_updates.py script, which reads installed versions via git describe for each local repo and compares them against the latest GitHub release tag from the API. It reports update_available only when the upstream tag is a stable release and semantically newer.

How to monitor PyPI package updates automatically?▼

The script queries the PyPI JSON API for the latest mem0ai version and compares it to the version reported by pip show. It filters out pre-release tags so only stable PyPI bumps trigger a notification.

Does this script automatically upgrade the installed tools?▼

No, the script never runs upgrades. It only reports update availability and marks auto_apply_ok as informational; all updates require manual or supervised application by the user.

Why does the check ignore nightly or beta releases?▼

The is_stable_release filter rejects tags containing nightly, alpha, beta, rc, pre, or dev so notifications only fire for stable upstream releases. This prevents noisy alerts from development builds.

What happens when the update check script fails?▼

On any exception the script catches the error and prints a JSON payload with should_notify set to true and a telegram_message describing the failure, then exits with code 1 so the automation alerts the user.