skill CX Codex

groove-utilities-memory-install — Claude Code skill: setup

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

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

Q: What does groove-utilities-memory-install do?

It creates Groove’s memory directories under `.groove/memory/` and reports the initialized paths.

Q: Which directories does groove-utilities-memory-install create?

It creates `daily`, `weekly`, `monthly`, `git`, `specs`, `learned`, and `docs` inside `.groove/memory/`. The `specs` and `docs` folders support `/groove-work-spec` and `/groove-work-doc`.

This skill creates Groove’s memory folder structure under .groove/memory/ and reports the initialized paths. Use it before tools that write project memory.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

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

Open on GitHub

What groove-utilities-memory-install does

The skill prepares Groove’s memory layout by creating daily, weekly, monthly, git, specs, learned, and docs under .groove/memory/. It then displays the paths that were initialized.

Directory creation uses mkdir -p, so existing folders do not block the setup. The specs directory supports /groove-work-spec, while docs is used by /groove-work-doc. The skill can use Read, Write, Edit, Glob, Grep, Bash(git:*), and AskUserQuestion.

The storage location is fixed at .groove/memory/. Any Groove component expecting another path will not read these directories.

What it helps with

create daily, weekly, and monthly memory folders
prepare storage for Git-related memory
set up folders for specs and reference documents
show the paths created during initialization

Example prompts for the agent

Initialize Groove memory in the current project and show the paths you created.
Create the .groove/memory/ structure for daily, weekly, and monthly records.
Prepare the memory, specs, and docs folders for Groove workflows.

How to install groove-utilities-memory-install

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

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

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-memory-install -a codex

2Manually: put the files in place

.agents/skills/groove-utilities-memory-install/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-memory-install -a cursor

2Manually: put the files in place

.cursor/skills/groove-utilities-memory-install/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install andreadellacorte/groove groove-utilities-memory-install

2Manually: put the files in place

.github/skills/groove-utilities-memory-install/SKILL.md

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-memory-install -a gemini-cli

2Platform CLI

gemini skills install https://github.com/andreadellacorte/groove --path skills/groove-utilities-memory-install

Manually: put the files in place

.devin/skills/groove-utilities-memory-install/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-memory-install -a opencode

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

Questions about groove-utilities-memory-install

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

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

What does groove-utilities-memory-install do?

It creates Groove’s memory directories under .groove/memory/ and reports the initialized paths.

Which directories does groove-utilities-memory-install create?

It creates daily, weekly, monthly, git, specs, learned, and docs inside .groove/memory/. The specs and docs folders support /groove-work-spec and /groove-work-doc.

Source text

SKILL.md · MIT

---
name: groove-utilities-memory-install
description: "Set up memory backend and configuration."
license: MIT
allowed-tools: Read Write Edit Glob Grep Bash(git:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

# groove-utilities-memory-install

## Outcome

Memory directories are created and ready for use.

## Acceptance Criteria

- `.groove/memory/daily/`, `.groove/memory/weekly/`, `.groove/memory/monthly/`, `.groove/memory/git/` exist
- `.groove/memory/specs/` directory exists (outcome specs; used by `/groove-work-spec`)
- `.groove/memory/learned/` directory exists
- `.groove/memory/docs/` directory exists (reference docs; used by `/groove-work-doc`)
- User is shown the initialized paths

## Constraints

- Memory path is always `.groove/memory/`
- Create directories if they do not exist:
  ```bash
  mkdir -p .groove/memory/daily .groove/memory/weekly .groove/memory/monthly .groove/memory/git .groove/memory/specs .groove/memory/learned .groove/memory/docs
  ```
- Report the initialized paths to user

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 set27

groove This skill turns plain-language requests into workflow commands. Use it for planning, task tracking, memory logs, and Groove administration. CX Codex +1 631installs groove-utilities-task-analyse Pulls tasks from your project backend and groups them by status, so you have something to write into daily memory. CX Codex +1 588installs groove-utilities-memory-log-daily Writes the end-of-day entry to .groove/memory/daily/YYYY-MM-DD.md: what got done, which commits landed, what carries over. CX Codex +1 581installs groove-admin-config Creates or updates .groove/index.md through a guided setup and applies Git rules for Groove. Use it before installing backends. CX Codex +1 580installs 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-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