Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From bopen-tools
Checks if the bopen-tools plugin is up to date by comparing local and GitHub versions. Returns status (current, outdated, etc.) and suggests update commands. Fast (~70ms).
npx claudepluginhub b-open-io/claude-plugins --plugin bopen-toolsHow this skill is triggered — by the user, by Claude, or both
Slash command
/bopen-tools:check-versionThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fast plugin version check — compares installed version against GitHub in ~70ms.
Checks for updates to the skills-for-fabric marketplace at session start. Compares local version against GitHub releases and shows changelog if updates are available. Useful for staying up-to-date with skill changes.
Audits Claude Code plugins for structure validation, frontmatter quality, deprecations, feature adoption, security patterns, and documentation. Ensures changelog compatibility and best practices for releases.
Compares installed plugin version with the latest available by reading the plugin registry and checking remote sources.
Share bugs, ideas, or general feedback.
Fast plugin version check — compares installed version against GitHub in ~70ms.
bash <skill-path>/scripts/check-version.sh
Returns JSON:
{
"plugin": "bopen-tools",
"org": "b-open-io",
"local_version": "1.0.82",
"remote_version": "1.0.83",
"status": "outdated",
"message": "Update available: 1.0.82 -> 1.0.83. Run: claude plugin update bopen-tools@b-open-io"
}
| Status | Meaning | Action |
|---|---|---|
current | Installed version matches GitHub | No action needed |
outdated | Newer version available on GitHub | Tell user to run the update command in the message field |
ahead | Local is newer than GitHub (dev environment) | No action needed |
not_installed | Plugin not found in cache | Tell user to install the plugin |
check_failed | Couldn't reach GitHub | Network issue — not critical, continue working |
The check is fast enough (~70ms) to run without noticeable delay. If status is outdated, tell the user and suggest the update command, but don't block on it — continue working with what's installed.