groove-utilities-check — Claude Code skill: features and setup
Checks GitHub for newer groove releases, compares semver tags against local files, and outputs an update command when outdated.
npx skills add andreadellacorte/groove --skill groove-utilities-check -a claude-codeWhat groove-utilities-check does
This skill checks whether your installed groove setup is behind the latest release on GitHub. It queries https://api.github.com/repos/andreadellacorte/groove/releases/latest and compares the resulting tag against the version noted in skills/groove/SKILL.md.
For speed, the skill first executes a bash script at scripts/check.sh. If bash is unavailable or exits non-zero, the model compares the semver strings directly after stripping leading letters. After every successful query, the current date gets saved to .groove/.cache/last-version-check.
Network interruptions and GitHub API rate limits fail silently without throwing fatal errors.
What it helps with
- check for newer groove releases on GitHub
- compare the current version in
skills/groove/SKILL.mdagainst the latest release tag - obtain the
/groove-admin-updatecommand when an update is available - log the verification date in
.groove/.cache/last-version-check
Example prompts for the agent
- Check if a newer version of groove is available on GitHub
- Run the groove update check script
- Verify my installed groove version against the latest release
How to install groove-utilities-check
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-check -a claude-code2Manually: put the files in place
~/.claude/skills/groove-utilities-check/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/groove-utilities-check/
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-check -a codex2Manually: put the files in place
.agents/skills/groove-utilities-check/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-check -a cursor2Manually: put the files in place
.cursor/skills/groove-utilities-check/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install andreadellacorte/groove groove-utilities-check2Manually: put the files in place
.github/skills/groove-utilities-check/SKILL.md1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-check -a gemini-cli2Platform CLI
gemini skills install https://github.com/andreadellacorte/groove --path skills/groove-utilities-checkManually: put the files in place
.devin/skills/groove-utilities-check/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-check -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about groove-utilities-check
How to install groove-utilities-check in Claude Code?
Run npx skills add andreadellacorte/groove --skill groove-utilities-check -a claude-code. The definition will be placed in ~/.claude/skills/groove-utilities-check/SKILL.md.
What notification appears when groove is outdated?
It prints a warning showing both current and latest versions, alongside the command /groove-admin-update.
How does the skill handle GitHub API rate limits?
If the API request fails due to connection issues or rate limits, the check skips execution silently without reporting errors.
Source text
SKILL.md · MIT
--- name: groove-utilities-check description: "Check if a newer version of groove is available on GitHub." license: MIT allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) Bash(mkdir:*) Bash(curl:*) Bash(python3:*) Bash(chmod:*) AskUserQuestion metadata: author: andreadellacorte bash: true --- <!-- groove:managed — do not edit; changes will be overwritten by groove update --> # groove-utilities-check ## Bash fast-path This skill has a bash script at `scripts/check.sh`. Run it directly for faster, model-free execution: ```bash bash .agents/skills/groove-utilities-check/scripts/check.sh ``` If the script exits 0, report its stdout and stop — do not continue with the steps below. If it exits non-zero or bash is unavailable, continue with the markdown steps. ## Outcome The latest published groove version is compared against the installed version. If a newer version is available, the user is clearly notified with the upgrade command. ## Acceptance Criteria - Latest tag is fetched from GitHub - Installed version (from `skills/groove/SKILL.md`) is compared against latest tag - If behind: user sees "⚠ New version of groove available: v<latest> (installed: v<current>) — run: `/groove-admin-update`" - If up to date: user sees "groove is up to date (v<current>)" - `.groove/.cache/last-version-check` is updated to today's date after check runs ## Constraints - Fetch latest release tag from: `https://api.github.com/repos/andreadellacorte/groove/releases/latest` - If the API call fails (no network, rate limit): skip silently — do not error - Compare version strings as semver (strip leading `v` before comparing) - Always write today's date to `.groove/.cache/last-version-check` after a successful API call - If `.groove/.cache/` does not exist, skip the date update
© andreadellacorte · MIT · andreadellacorte/groove