qianwen-update-check

Compare local QianWen-AI skill pack version against GitHub releases.

67|4|Updated May 9, 2026
One-click install
npx skills add https://github.com/QianWen-AI/qianwen-ai --skill qianwen-update-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qianwen-update-check
Source: https://github.com/QianWen-AI/qianwen-ai/tree/main/skills/ops/qianwen-update-check
Command: npx skills add https://github.com/QianWen-AI/qianwen-ai --skill qianwen-update-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Monitors the local QianWen-AI skill pack version and notifies users when a newer release is available.

Core Features & Use Cases

  • Reads the locally installed version from version.json.
  • Fetches the latest version metadata from GitHub.
  • Compares versions using semantic versioning and signals updates.
  • Implements a 24-hour rate limit via a state file to balance accuracy and network usage.
  • Triggered automatically by other skills and can be run manually via the CLI.

Quick Start

Run the update check to see if a newer version is available.

Frequently Asked Questions about qianwen-update-check

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

FAQPage Schema
How do I check for updates on a Python GitHub CLI tool?

To check for updates on a Python GitHub CLI tool, you can use an automated script that reads the local version.json, fetches remote release metadata via GitHub, and compares them using semantic versioning to signal available updates.

How does semantic versioning comparison work for GitHub releases?

Semantic versioning comparison works by fetching remote GitHub release metadata and evaluating it against the locally installed version. It determines if a newer release exists by parsing and comparing the major, minor, and patch version numbers.

How to avoid excessive GitHub API requests during automated version checks?

To avoid excessive GitHub API requests during automated version checks, implement a 24-hour rate limit using a state file. This restricts network usage by preventing repeated remote metadata fetches within the same day.

Can I trigger an automated update check from other skills?

Yes, you can trigger an automated update check from other skills and automation workflows. The Python-based updater runs automatically in the background and can also be executed manually via the command line interface.

What limitations exist when using a state file for update rate limiting?

A limitation of using a state file for update rate limiting is the enforced 24-hour delay. This 24-hour rate limit balances accuracy and network usage but prevents immediate, real-time detection of newly published GitHub releases.