Skip to main content
affpapa.org
RU EN
skill CX Codex

groove-utilities-task-doctor — Claude Code skill: task checks

Audits task-backend setup, command-line access, authentication, and reachability. Use it before relying on task commands in a repository.

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

What groove-utilities-task-doctor does

This skill walks through the task backend setup in order. It checks for .groove/index.md at the Git root, validates tasks.backend, and tests the matching CLI. For beans, that means beans version and .beans.yml; linear needs its CLI and auth token; github is checked with gh --version and gh auth status.

It then performs a lightweight read against the selected service and, for tasks: beans, looks for the task section in AGENTS.md. Every result gets a ✓ or ✗, with a concrete remediation command beside failures. The skill reports problems only; it does not modify the repository.

When tasks: none is configured, it prints tasks: none — task commands disabled and stops. That is a deliberate no-op, so backend connectivity checks are skipped.

What it helps with

  • verify .groove/index.md at the Git root
  • catch an invalid tasks.backend value
  • check whether beans, linear, or gh is installed
  • test task-backend authentication and reachability
  • confirm the task section exists in AGENTS.md

Example prompts for the agent

  • Check the task backend in this repository and report every result.
  • Audit the linear setup, including its CLI, auth token, and access to one issue.
  • Inspect tasks.backend: beans; report fixes without changing any files.

How to install groove-utilities-task-doctor

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-task-doctor -a claude-code

2Manually: put the files in place

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

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

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about groove-utilities-task-doctor

How do I install groove-utilities-task-doctor in Claude Code?

Run npx skills add andreadellacorte/groove --skill groove-utilities-task-doctor -a claude-code, then check ~/.claude/skills/groove-utilities-task-doctor/SKILL.md.

What does groove-utilities-task-doctor do?

It audits task-backend configuration, the required CLI, authentication, service access, and the relevant AGENTS.md section. Results use ✓ or ✗, and failures include a suggested remediation command.

Which platforms can run this skill?

The skill can be installed for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.

Source text

SKILL.md · MIT 
---
name: groove-utilities-task-doctor
description: "Check task backend health and connectivity."
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-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)

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

## Remediation hints

| Failure | Remediation |
|---|---|
| `.groove/index.md` missing | `/groove-utilities-task-config` or `/groove config` |
| Backend not installed | `/groove-utilities-task-install` |
| `.beans.yml` missing | `/groove-utilities-task-install` (will scaffold) |
| Backend unreachable | Check auth / network, re-run `/groove-utilities-task-install` |
| `AGENTS.md` section missing | `/groove install` |

## Constraints

- Report all checks even if an early one fails — give the full picture
- Do not attempt to fix issues — report and suggest only
- If `tasks: none`, show one green line: "tasks: none — task commands disabled" and exit

© andreadellacorte · MIT · andreadellacorte/groove

Similar skills

All skills for Agent setup: memory, context, orchestration →
setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs ask-matt Matt Pocock Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug. 766,587installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. 711,230installs writing-plans Jesse Vincent This skill turns requirements for a multi-step task into an implementation plan before code changes begin. It helps when another engineer needs exact files, interfaces, and checks. CX Codex 282,859installs caveman-review JuliusBrussee Turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 411,800installs caveman-compress JuliusBrussee Compresses CLAUDE.md, todo lists, and other prose files into a shorter format while retaining a readable backup. CX Codex +1 411,500installs

From the same set39

groove-admin-doctor Runs Groove health checks for the repository, versions, companion skills, symlinks, and native hooks. It helps locate setup issues before work starts. CX Codex +1 571installs groove-daily-start Prepares the workday: reviews recent days, creates today's memory file, loads tasks and lays out the agenda. CX Codex +1 571installs groove-daily-end Archives daily git activity, writes structured project memory records, and executes custom wrap-up hooks. CX Codex +1 557installs groove-utilities-memory-doctor Checks Groove memory backend health and configuration. Useful when context logs fail to save or after updating repository workflows. CX Codex +1 554installs groove-work-brainstorm Clarifies scope through conversation, enforces YAGNI to curb creep, and flags open questions before formal project planning starts. CX Codex +1 550installs groove-utilities-task-update Updates an existing task’s status, body, or metadata in the configured backend. It keeps progress notes and requires confirmation before completion. CX Codex +1 545installs groove-work-review This skill reviews completed work against its plan, records lessons, and returns an accept or rework decision with reasons. CX Codex +1 544installs groove-work-plan Researches your codebase and writes a concrete implementation plan with ordered steps, file paths and function names. Meant to run after brainstorming. CX Codex +1 544installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

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