Groove Admin Update

Keeps your local groove installation in sync with upstream releases by pulling the latest skills and running any state migrations you've missed. It fetches the actual release tag from GitHub to verify you're getting the current version, not a stale cached copy from npx, and retries up to three times if needed. Migrations run in order and checkpoint after each one, so a failed upgrade won't leave you in limbo. It also refreshes the platform symlinks between .agents/skills and .claude/skills or .cursor/skills afterward. This is what groove maintainers run after publishing a release, but anyone using groove should run it periodically to stay current with fixes and new features.

skills.sh installs: 528
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-admin-update --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-admin-update

Maintainers (andreadellacorte/groove repo): After publishing a new GitHub Release, run this from the groove repo root so checked-in .agents/skills/groove* matches what npx skills add andreadellacorte/groove installs — see CONTRIBUTING.md (“Publish release”). Do not use manual rsync from skills/ for that.

Outcome

All pending migrations are applied to the user's local groove state in version order. .groove/index.md reflects the current installed groove version.

Acceptance Criteria

groove-version: in .groove/index.md matches version: in skills/groove/SKILL.md after update
Each pending migration was applied in order
groove-version: updated after each successful migration (partial progress is recoverable)
If already up to date, reports clearly and exits
Source-of-truth check: "up to date" is only reported when the installed skill version equals the latest GitHub release; if the add step left an older version on disk (e.g. cached or default branch), the user is warned and told how to fix it