Groove Utilities Task Config

This handles the configuration side of a task management integration system that can connect to Beans, Linear, GitHub, or run standalone. It reads and writes a single frontmatter key in `.groove/index.md`, shows you the current backend when called without arguments, and swaps it out when you provide a new one. The nice touch is that it validates your input against the four allowed values and won't let you fat-finger something invalid. If you're building a workflow that needs to switch between different task backends without manually editing config files, this gives you an interactive way to do it. Just know you'll need to run the separate install skill afterward to actually wire up the new backend.

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

View on GitHub

Install

$ npx -y skills add andreadellacorte/groove --skill groove-utilities-task-config --agent claude-code

Installs into .claude/skills of the current project.

Files

groove-utilities-task-config

Outcome

The current task backend configuration is shown to the user, or updated based on provided arguments. After update, user is prompted to run /groove-utilities-task-install if the backend changed.

Acceptance Criteria

Current tasks.backend value is displayed with no arguments
Backend is updated in .groove/index.md frontmatter when new value provided
User is reminded to run /groove-utilities-task-install if backend changed

Constraints

Read and write .groove/index.md frontmatter tasks.backend key only
Valid values: beans, linear, github, none
Reject unknown backend values with a helpful error listing valid options
If .groove/index.md does not exist, create from skills/groove/templates/index.md with defaults
Do not modify any other keys in .groove/index.md