groove-admin-config
Create or update .groove/index.md config interactively. Run before groove install.
- Installs
- 580
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/andreadellacorte/groove --skill groove-admin-config- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads groove-admin-config automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.mdexists with all config keys populated- Each key was either confirmed by the user or accepted as default
- Git strategy is applied (
.groove/.gitignorewritten) 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:
- Write
.groove/index.mdwith confirmed values andgroove-version: <installed version> - Apply git strategy — write
.groove/.gitignore(see constraints) - Show summary of written config
- Tell user: "Run
/groove-admin-installto install backends."
Constraints
- If
.groove/index.mdalready exists, pre-fill each question with the current value - Always write
groovebook:(defaultandreadellacorte/groovebook; blank = disabled). Memory path (.groove/memory/) and specs path (.groove/memory/specs/) are hardcoded — do not prompt for them. - If
--defaultsis passed, apply all defaults without any prompting — used bygroove-admin-installfor 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 fromskills/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
.gitignoreautomatically — flag it for the user to resolve
FAQ
What does the groove-admin-config skill do?
Create or update .groove/index.md config interactively. Run before groove install.
How do I install groove-admin-config?
Run npx skills add https://github.com/andreadellacorte/groove --skill groove-admin-config in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/groove-admin-config/ (personal) or .claude/skills/groove-admin-config/ (project).
Which AI agents can use groove-admin-config?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is groove-admin-config safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains groove-admin-config?
It is published by andreadellacorte in andreadellacorte/groove. It has 580 recorded installs.
More from andreadellacorte/groove
groove
andreadellacorte/groove
Groove engineering workflow system. Top-level entry point. Use groove-daily-, groove-work-, groove-utilities-, groove-admin- for all workflow and admin commands.
groove-utilities-task-analyse
andreadellacorte/groove
Analyse task status and distribution across the configured backend.
groove-utilities-memory-install
andreadellacorte/groove
Set up memory backend and configuration.
groove-admin-install
andreadellacorte/groove
Install groove backends, companions, and AGENTS.md bootstrap. Run once per repo.
groove-utilities-memory-log-daily
andreadellacorte/groove
Write the daily memory log entry. Use at end of day to record what happened.
groove-utilities-task-install
andreadellacorte/groove
Set up task backend and configuration.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.