groove-utilities-task-doctor

groove-utilities-task-doctor is a skill for Claude Code from andreadellacorte/groove. It costs 15 tokens per session (524 once invoked), scanned A, original, MIT.

A health check for the system that stores groove tasks, such as Beans, Linear, or GitHub Issues.

In plain words
What is it for?
Use it to verify the project configuration, task CLI, backend settings, and backend connectivity.
Why use it?
It identifies missing configuration, command-line tools, authentication, or network access before task operations fail.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions AGENTS.md.

Good fit Use it to verify the project configuration, task CLI, backend settings, and backend connectivity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andreadellacorte/groove/groove-utilities-task-doctor
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add andreadellacorte/groove --skill groove-utilities-task-doctor
Clone the repo
git clone --depth 1 https://github.com/andreadellacorte/groove

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for groove-utilities-task-doctor

README.md
[![agentmods](https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-task-doctor/github.svg)](https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-task-doctor)
Your own site
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-task-doctor"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-task-doctor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for groove-utilities-task-doctor

Your own site · 80×15
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-task-doctor"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-task-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk warn 10 Mar 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00524
Opus 5 $0.00008 $0.00262
Sonnet 5 $0.00003 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured 11d ago against content hash c91d077d1be2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

groove-utilities-task-doctor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/groove-utilities-task-doctor/SKILL.md · 56 lines

What it actually says

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
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 56 lines · 15 tokens per session scan A c91d077d1be2

Subscribe to this mod's changes

groove-utilities-task-doctor is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 524 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

triage-issue

Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…

atlassian/atlassian-mcp-server · 116 tokens

bug-triage

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

Donchitos/Claude-Code-Game-Studios · 59 tokens

investigation

Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).

me2resh/apexyard · 26 tokens

browse-flows

Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.

microsoft/power-platform-skills · 31 tokens

operating-cadence

Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…

cbrock84/headcount · 95 tokens