groove-utilities-task-config — Claude Code skill: how to install
Displays or updates the active task tracking backend in Groove. Useful when switching project tasks to Linear or GitHub.
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a claude-codeWhat groove-utilities-task-config does
This skill manages the tasks.backend setting inside .groove/index.md. Running it without arguments prints the current configuration. It writes new values directly to frontmatter. Other keys remain untouched.
Accepted backend values are beans, linear, github, and none. Any unrecognized input triggers an immediate error. If .groove/index.md is missing, the skill generates it automatically from skills/groove/templates/index.md using default values.
Updating the configuration file is not enough. When the backend changes, the skill prompts you to execute /groove-utilities-task-install. Without this step, the new task integration will not work.
What it helps with
- inspect the current task backend setting
- switch the issue tracker to
linearorgithub - disable external trackers using
none - generate
.groove/index.mdfrom the template if missing
Example prompts for the agent
- Show the current task backend setting
- Switch task backend to linear
- Set tasks.backend to github
How to install groove-utilities-task-config
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a claude-code2Manually: put the files in place
~/.claude/skills/groove-utilities-task-config/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/groove-utilities-task-config/
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a codex2Manually: put the files in place
.agents/skills/groove-utilities-task-config/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a cursor2Manually: put the files in place
.cursor/skills/groove-utilities-task-config/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install andreadellacorte/groove groove-utilities-task-config2Manually: put the files in place
.github/skills/groove-utilities-task-config/SKILL.md1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a gemini-cli2Platform CLI
gemini skills install https://github.com/andreadellacorte/groove --path skills/groove-utilities-task-configManually: put the files in place
.devin/skills/groove-utilities-task-config/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -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-task-config
How to install groove-utilities-task-config in Claude Code?
Run npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a claude-code.
What does groove-utilities-task-config do?
The skill reads and updates the tasks.backend key in the .groove/index.md frontmatter. It lets you switch task tracking providers or disable the integration.
Which task backends are supported?
Valid options are beans, linear, github, and none. Any other input is rejected with an error displaying the valid choices.
Source text
SKILL.md · MIT
--- name: groove-utilities-task-config description: "Configure task backend settings interactively." license: MIT allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) AskUserQuestion metadata: author: andreadellacorte --- # 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`
© andreadellacorte · MIT · andreadellacorte/groove