Skip to content
Agentmart
Submit a tool

groove-admin-config

Create or update .groove/index.md config interactively.

Skill by andreadellacorte

IndexedMIT★ 6
Write a review

Chalk Labs

Need help deploying groove-admin-config?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/andreadellacorte-groove-admin-config

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Create or update .groove/index.md config interactively. Run before groove install.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/groove-admin-config

Tools it pre-approves 12

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • Bash(git:*)
  • Bash(beans:*)
  • Bash(gh:*)
  • Bash(linear:*)
  • Bash(npx:*)
  • Bash(mkdir:*)
  • AskUserQuestion

What's inside

Skill name
groove-admin-config
Description
Create or update .groove/index.md config interactively. Run before groove install.
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
Instructions
76 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves some shell commands

Files (1)

  • SKILL.md

SKILL.md (first lines)

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

# groove-admin-config

## Outcome

`.groove/index.md` is created or updated with values confirmed by the user. The git strategy is applied immediately. User is ready to run `/groove-admin-install`.

## Acceptance Criteria

- `.groove/index.md` exists with all config keys populated
- Each key was either confirmed by the user or accepted as default
- Git strategy is applied (`.groove/.gitignore` written) before exiting
- User is shown a summary of the final config and told to run `/groove-admin-install`

## Steps

If `--defaults` is passed: skip all prompts, apply all defaults, and proceed directly to writing the config (step 1 of "After all keys are confirmed"). Report the defaults being applied.

Otherwise, walk the user through each config key in order. For each key: show the current value (or default if new), explain what it does, and ask to confirm or change.

### Keys and defaults

| Key | Default | Options | Question to ask |
|---|---|---|---|
| `tasks.storage` | `beans` | `beans \| linear \| github \| none` | "Which task backend? beans tracks tasks as markdown files in your repo." |
| `tasks.list_limit` | `15` | positive integer | "Max tasks shown by task-list? (default: 15)" |
| `tasks.analyse_limit` | `30` | positive integer | "Max tasks shown by task-analyse? (default: 30)" |
| `memory.review_days` | `5` | positive integer | "How many recent business days to review at daily start? (default: 5)" |
| `git.memory` | `ignore-all` | `ignore-all \| hybrid \| commit-all` | "Git strategy for memory logs? ignore-all keeps them local, hybrid commits logs but ignores sessions, commit-all commits everything." |
| `git.tasks` | `ignore-all` | `ignore-all \| commit-all` | "Git strategy for task files (.groove/tasks/)? ignore-all keeps them local, commit-all tracks them in git." |
| `git.hooks` | `commit-all` | `ignore-all \| commit-all` | "Git strategy for hooks (.groove/hooks/)? commit-all shares hooks with the team, ignore-all keeps them local." |
| `groovebook` | `andreadellacorte/groovebook` | `<owner>/<repo>` or blank | "Groovebook repo for sharing learnings? Default: andreadellacorte/groovebook. Leave blank to disable." |

After all keys are confirmed:

1. Write `.groove/index.md` with confirmed values and `groove-version: <installed version>`
2. Apply git strategy — write `.groove/.gitignore` (see constraints)
3. Show summary of written config
4. Tell user: "Run `/groove-admin-install` to install backends."

## Constraints

- If `.groove/index.md` already exists, pre-fill each question with the current value
- Always write `groovebook:` (default `andreadellacorte/groovebook`; blank = disabled). Memory path (`.groove/memory/`) and specs path (`.groove/memory/specs/`) are hardcoded — do not prompt for them.
- If `--defaults` is passed, apply all defaults without any prompting — used by `groove-admin-install` for zero-friction first-time setup
- If other arguments are provided (e.g. `tasks=linear git.memory=hybrid`), apply them without prompting and use defaults for any unspecified keys
- Always write `groove-version:` matching the installed version from `skills/groove/SKILL.md`

### Git strategy → `.groove/.gitignore`

After writing `.groove/index.md`, generate `.groove/.gitignore` from the `git.*` sub-keys:

| Component | Strategy | Entry added to `.groove/.gitignore` |
|---|---|---|
| `git.memory` | `ignore-all` | `memory/` |
| `git.memory` | `hybrid` | `memory/sessions/` |
| `git.memory` | `commit-all` | _(none)_ |
| `git.tasks` | `ignore-all` | `tasks/` |
| `git.tasks` | `commit-all` | _(none)_ |
| `git.hooks` | `ignore-all` | `hooks/` |
| `git.hooks` | `commit-all` | _(none)_ |

Write the generated entries to `.groove/.gitignore`, replacing the file entirely. If no entries are generated (all `commit-all`), write an empty file with a comment: `# groove git strategy: commit-all`.

Always append these lines at the end of `.groove/.gitignore`, regardless of strategy:
```
# cache — always local
.cache/*
!.cache/.gitkeep
```

- If `.groove/` is listed in the root `.gitignore`, warn the user: "Note: `.groove/` is in your root .gitignore — any commit-all strategies require removing it."
- Do not modify the root `.gitignore` automatically — flag it for the user to resolve

From andreadellacorte/groove, MIT.

More from andreadellacorte/groove

Signals

Stars
6
Forks
0
Open issues
0
Last commit (this folder)
Mar 15, 2026 (7 months ago)
Last release
Jul 4, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from andreadellacorte

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get groove-admin-config running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying groove-admin-config?

CallGet help
Cite this page

groove-admin-config skill. Agent Mart. https://agentmart.dev/skills/andreadellacorte-groove-admin-config (last updated 2026-10-24)