Skip to main content
skill CX Codex

groove-admin-install — Claude Code skill: how to install

groove-admin-install bootstraps Groove backends, companion tools, and session hooks for a repository. Run it once during project setup.

MIT 586 installs ★ 6 updated 2026-07-24

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

What groove-admin-install does

This skill prepares a repository for Groove agent workflows. It verifies or generates .groove/index.md with default values, invokes task and memory backend installers, and bootstraps the AGENTS.md context file.

Execution follows strict dependency order. First, task and memory backends deploy. Next, the skill installs three companion skills via npx: find-skills, agent-browser, and pdf-to-markdown. It then creates platform symlinks inside .claude/skills/ and .cursor/skills/ using ln -sfn, pointing them to .agents/skills/. Finally, it scaffolds .groove/hooks/ with start and end session hooks.

Without npx in the environment, the setup halts. The skill treats the bootstrap as incomplete until all three companion tools exist and editor symlinks pass verification.

What it helps with

  • bootstrap Groove architecture in a new project
  • link skill directories into Claude Code and Cursor
  • fetch required companion skills find-skills, agent-browser, and pdf-to-markdown
  • scaffold lifecycle session hooks in .groove/hooks

Example prompts for the agent

  • Run /groove-admin-install to initialize Groove for this project
  • Set up Groove backends and editor symlinks using /groove-admin-install

How to install groove-admin-install

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/groove-admin-install/SKILL.md

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

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

Questions about groove-admin-install

How to install groove-admin-install in Claude Code?

Run npx skills add andreadellacorte/groove --skill groove-admin-install -a claude-code in your terminal.

What does groove-admin-install do?

It initializes project configuration, installs task and memory backends, downloads required companion skills, creates editor symlinks, and generates session hooks.

Which companion skills does groove-admin-install fetch?

The skill installs find-skills, agent-browser, and pdf-to-markdown into .agents/skills/. Bootstrap fails if any of these three cannot be verified.

Source text

SKILL.md · MIT
---
name: groove-admin-install
description: "Install groove backends, companions, and AGENTS.md bootstrap. Run once per repo."
license: MIT
allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) Bash(mkdir:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

<!-- groove:managed — do not edit; changes will be overwritten by groove update -->

# groove-admin-install

## Outcome

All groove backends are installed in dependency order, **companion skills and groove skill symlinks are present** (first install is not complete without them), AGENTS.md contains the session bootstrap, and the repo is ready for use.

## Acceptance Criteria

- Task and memory backends installed (or clearly reported if a step failed)
- **Companion skills installed** (find-skills, agent-browser, pdf-to-markdown) — required; verify each `SKILL.md` exists after step 4
- **Platform symlinks** — `.claude/skills/groove*` and `.cursor/skills/groove*` point at `.agents/skills/groove*` — required on every install run
- User sees a summary of what was installed, including ✓/✗ for companions and symlinks

## Steps

Run in order:

1. If `.groove/index.md` does not exist, run `/groove-admin-config --defaults` to create it with all defaults (no prompts)
2. Run `/groove-utilities-task-install` — installs the configured task backend (e.g. beans)
3. Run `/groove-utilities-memory-install` — creates memory directories
4. **Install companion skills (mandatory — do not skip):** On first install and every later run, ensure these exist under `.agents/skills/`. If `SKILL.md` is missing, run the matching `npx skills add` command; on transient failure, retry once, then report failure (install is **not** complete until all three succeed).
   - **find-skills** (downloaded): `test -f .agents/skills/find-skills/SKILL.md` or `npx skills add https://github.com/vercel-labs/skills --skill find-skills`
   - **agent-browser** (downloaded): `test -f .agents/skills/agent-browser/SKILL.md` or `npx skills add https://github.com/vercel-labs/agent-browser --skill agent-browser`
   - **pdf-to-markdown** (embedded): `test -f .agents/skills/pdf-to-markdown/SKILL.md` or `npx skills add andreadellacorte/groove --skill pdf-to-markdown`
   - Afterward, verify: `test -f` each of the three `SKILL.md` paths — if any missing, stop and report install incomplete (do not claim success).
   - Report each as installed / already-present / failed
5. **Sync platform skill directories via symlinks (mandatory — do not skip):** Groove skills must be linked into each editor’s skills tree so `groove-*` commands resolve.
   - Create parent dirs if missing: `mkdir -p .claude/skills .cursor/skills` (Claude Code expects `.claude/skills/`; Cursor expects `.cursor/skills/`)
   - For each directory in `.agents/skills/` that starts with `groove`:
     - Create `.claude/skills/<name>` as a symlink → `../../.agents/skills/<name>`
     - Create `.cursor/skills/<name>` as a symlink → `../../.agents/skills/<name>`
   - Run: `mkdir -p .claude/skills .cursor/skills && for skill in .agents/skills/groove*; do name=$(basename "$skill"); ln -sfn "../../.agents/skills/$name" ".claude/skills/$name"; ln -sfn "../../.agents/skills/$name" ".cursor/skills/$name"; done`
   - Note: use `ln -sfn` (no-dereference) — `ln -sf` on an existing directory symlink follows the symlink and creates a nested symlink inside the target directory
   - Verify: at least one `groove-*` name exists under `.agents/skills/` and matching symlinks exist under `.claude/skills/` and `.cursor/skills/`
   - Report: "✓ platform symlinks updated (.claude/skills/, .cursor/skills/)" or report failure
6. Scaffold hooks and cache directories:
   - Create `.groove/hooks/` if it does not exist
   - Create `.groove/.cache/` if it does not exist (with a `.gitkeep`)
   - If `.groove/hooks/start.md` does not exist, create it with:
     ```markdown
     # Hook: Session Start

     Runs automatically at the end of `/groove-daily-start`.
     Add items to `## Actions` to automate session-start tasks.

     ## Actions

     <!-- Add actions here, one per line. Examples:
     - Run `git fetch --all` to refresh remote refs
     - Print "Good morning — groove is ready"
     -->
     ```
   - If `.groove/hooks/end.md` does not exist, create it with:
     ```markdown
     # Hook: Session End

     Runs automatically at the end of `/groove-daily-end`.
     Add items to `## Actions` to automate session-end tasks.

     ## Actions

     <!-- Add actions here, one per line. Examples:
     - Run `git push` to push today's commits
     - Print "Session closed — see you tomorrow"
     -->
     ```
   - Report hooks: created / already-present
7. Apply git strategy — write `.groove/.gitignore` from `git.*` sub-keys in `.groove/index.md` (see `/groove-admin-config` for rules)

## Constraints

- Read `.groove/index.md` for `tasks.backend` and `git.*` config before running
- If `.groove/index.md` does not exist, `/groove-admin-config` is run first (step 1) to create it
- Dependency order for backends must be respected: task → memory → companions
- Each step reports installed / already-present / failed
- `AGENTS.md` update is additive per section — preserve all other content
- If task or memory install fails, report it clearly and continue — user may still need companions + symlinks
- **Steps 4–5 (companion skills + symlinks) are required for a successful install:** do not report "install complete" until both steps succeeded. This is intentional: first-time bootstrap must leave skills discoverable in Cursor and Claude Code.
- Companion skills (find-skills, agent-browser, pdf-to-markdown) are hardcoded here, not read from any config file
- Report a final summary (include platform symlinks line):
  ```
  ✓ task backend (beans)
  ✓ memory backend — memory dirs ready
  ✓ companion: find-skills
  ✓ companion: agent-browser
  ✓ companion: pdf-to-markdown
  ✓ platform symlinks (.claude/skills/, .cursor/skills/)
  ✓ hooks: .groove/hooks/ ready
  ```

© andreadellacorte · MIT · andreadellacorte/groove

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set42

The whole set →
groove This skill turns plain-language requests into workflow commands. Use it for planning, task tracking, memory logs, and Groove administration. CX Codex +1 633installs groove-utilities-task-analyse 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 590installs groove-utilities-memory-install The groove-utilities-memory-install skill creates Groove’s memory folder structure under .groove/memory/ and reports the initialized paths. Use it before tools that write project memory. CX Codex +1 587installs groove-utilities-memory-log-daily 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 583installs groove-admin-config 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 581installs groove-utilities-task-list groove-utilities-task-list — a skill for Claude Code and five other platforms that pulls active tasks from a configured backend and groups them by status. In-progress work surfaces first, blocked tasks show what they are waiting on. CX Codex +1 579installs groove-admin-doctor 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 573installs groove-daily-start groove-daily-start prepares the workday: reviews recent days, creates today's memory file, loads tasks and lays out the agenda. CX Codex +1 573installs

Project sponsors

Companies that keep this analytics open