Groove Utilities Task Doctor

This runs a series of health checks on your Groove task backend setup and tells you exactly what's broken. It verifies your config file exists, checks if the right CLI is installed (beans, Linear, or GitHub), confirms auth is working, and tests actual connectivity with a lightweight API call. Each failure comes with a specific remediation command to run next. The smart bit is it reports everything at once rather than failing fast, so you get the full picture of what needs fixing. If you've set tasks to none, it just confirms that and exits green. Useful when onboarding teammates or debugging why task commands suddenly stopped working.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

groove-utilities-task-doctor

Outcome

All task backend health checks pass. User knows if the task backend is correctly configured, installed, and reachable.

Acceptance Criteria

Each check is reported with ✓ or ✗
Each failure includes a specific remediation command
Checks cover config, CLI installation, and reachability

Checks (run in order)

.groove/index.md exists at git root
tasks.backend key is present and has a valid value (beans, linear, github, or none)
If tasks.backend: none — report no-op and exit (all green)
Backend CLI is installed:
- beans: beans version
- linear: linear --version
- github: gh --version
Backend-specific config file exists:
- beans: .beans.yml at git root
- linear: auth token configured
- github: gh auth status
Backend is reachable (lightweight read operation):
- beans: beans list --json (or equivalent)
- linear: list one issue
- github: gh issue list --limit 1
AGENTS.md contains  section (if tasks: beans)