Skip to main content
skill CX Codex

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add andreadellacorte/groove --skill groove-utilities-task-config -a claude-code
Open on GitHub

What 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 linear or github
  • disable external trackers using none
  • generate .groove/index.md from 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-code

2Manually: put the files in place

~/.claude/skills/groove-utilities-task-config/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/groove-utilities-task-config/

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

Similar skills

All skills for Notes, tasks and projects →

From the same set39

groove-utilities-memory-log-git Writes a Git session summary to .groove/memory/git/. Use it when daily repository activity should stay in the project memory. CX Codex +1 538installs groove-utilities-check Checks GitHub for newer groove releases, compares semver tags against local files, and outputs an update command when outdated. CX Codex +1 537installs groove-utilities-memory-log-monthly Turns the month's daily memory files into one summary at .groove/memory/monthly/YYYY-MM.md, with themes, outcomes and learnings. CX Codex +1 537installs groove-work-exec This skill takes a finished implementation plan and writes the code, tests and docs for it, logging progress in your task backend. Use it once planning is done. CX Codex +1 536installs groove-utilities-task-archive Archives completed and scrapped tasks in the configured backend. Use it when you want to close a batch of finished work with a confirmation step. CX Codex +1 532installs groove-admin-claude-hooks Installs groove’s native shell hooks in .claude/settings.json. They track git activity, prepare session-capture drafts, and guard managed paths. CX Codex +1 530installs groove-utilities-memory-mistakes This skill turns an agent mistake into a tracked incident, fixes its cause, and records the lesson in project memory. Use it to stop repeat errors. CX Codex +1 529installs groove-admin-update Pulls the latest groove skills and applies pending migrations to your local groove state. Useful when a new release lands but your config and memory are still on the old one. CX Codex +1 528installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor