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

groove-utilities-memory-doctor — Claude Code skill: how to install

Checks Groove memory backend health and configuration. Useful when context logs fail to save or after updating repository workflows.

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

What groove-utilities-memory-doctor does

This skill inspects the workspace to verify that the Groove memory file structure is intact. It evaluates five locations in order: .groove/index.md at the git root, .groove/memory/, the log subdirectories (daily/, weekly/, monthly/, git/), .groove/memory/specs/, and the warm tier in learned/.

Every check is marked with a checkmark or a cross. The tool evaluates all items in sequence even when an early step fails. You get a complete status report in one pass.

The tool never alters your files directly. Instead, it suggests the required command for each missing component, such as /groove-admin-config, /groove-utilities-memory-log-daily, /groove-utilities-memory-install, or /groove-admin-update for the 0.11.5 to 0.12.0 migration.

What it helps with

  • verify Groove memory directory structure
  • identify missing log folders and specifications
  • get specific remediation commands for missing paths
  • check for the learned tier directory after migrations

Example prompts for the agent

  • Run groove-utilities-memory-doctor to inspect our memory setup
  • Check if all Groove memory directories exist
  • Diagnose why Groove memory logs are failing

How to install groove-utilities-memory-doctor

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

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

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

Questions about groove-utilities-memory-doctor

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

Run npx skills add andreadellacorte/groove --skill groove-utilities-memory-doctor -a claude-code.

What does groove-utilities-memory-doctor do?

It reviews five file paths in .groove/ and marks each with a checkmark or cross. When a folder is missing, it outputs the remediation command needed to create it.

Does this skill fix broken directories automatically?

No. By design, it only reports issues and suggests remediation commands such as /groove-admin-config or /groove-utilities-memory-install.

Source text

SKILL.md · MIT 
---
name: groove-utilities-memory-doctor
description: "Check memory backend health and configuration."
license: MIT
allowed-tools: Read Write Edit Glob Grep Bash(git:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

# groove-utilities-memory-doctor

## Outcome

All memory health checks pass. User knows if the memory file structure is correctly configured and accessible.

## Acceptance Criteria

- Each check is reported with ✓ or ✗
- Each failure includes a specific remediation command
- Checks cover memory path and directory structure

## Checks (run in order)

1. `.groove/index.md` exists at git root
2. Memory base path exists (`.groove/memory/`)
3. Memory log subdirectories exist: `daily/`, `weekly/`, `monthly/`, `git/`
4. Specs directory exists: `.groove/memory/specs/` (used by `/groove-work-spec`)
5. `learned/` directory exists: `.groove/memory/learned/` (warm memory tier)

## Remediation hints

| Failure | Remediation |
|---|---|
| `.groove/index.md` missing | `/groove-admin-config` |
| Memory path missing | `/groove-utilities-memory-log-daily` (will create on first run) |
| Log subdirectory missing | `/groove-utilities-memory-log-daily` |
| Specs directory missing | `/groove-utilities-memory-install` |
| `learned/` missing | `/groove-admin-update` (migration 0.11.5→0.12.0 creates it) |

## Constraints

- Report all checks even if an early one fails
- Do not attempt to fix issues — report and suggest only

© 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-utilities-task-list Pulls active tasks from your configured backend and shows what is in progress, ready or blocked. Handy as a daily starting view. CX Codex +1 577installs 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-task-doctor Audits task-backend setup, command-line access, authentication, and reachability. Use it before relying on task commands in a repository. CX Codex +1 551installs 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

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