skills/groove-utilities-task-install/SKILL.md
Set up task backend and configuration.
npx skillsauth add andreadellacorte/groove groove-utilities-task-installInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The configured task backend is installed and verified reachable. User is informed of what was installed and how to use it.
tasks.storage: nonetasks.storage from .groove/index.md to determine backend (if the key is still named tasks.backend from an older config, treat it as the storage value). If the key is missing or invalid, you may pause and use AskUserQuestion so the user can choose a backend (beans, linear, github, or none); then ensure .groove/index.md is updated accordingly (via /groove-admin-config or an equivalent edit) before continuing.tasks.storage: none, print friendly no-op message and exitbeans: hmans/beans — Installation sectionlinear: schpet/linear-cli — install section (third-party CLI; not Linear’s hosted docs)github: GitHub CLIbeans version, linear --version / linear --help, or gh version / gh auth status as appropriate)tasks.storage: beans and .beans.yml does not exist at git root:
beans init to initialise the task store and generate .beans.yml with beans defaults[PROJECT_PREFIX] from the git repo name (last path component of git remote get-url origin, stripped of .git, uppercased, non-alphanumeric stripped) — e.g. groove → GRV; fall back to the directory name if no remoteprefix: field in the generated .beans.yml to the derived prefix (e.g. GRV-)path: in .beans.yml to .groove/tasks so the task store lives under groove (aligned with git.tasks and .groove/.gitignore). Create .groove/tasks if it does not exist. If the default .beans directory was created and is non-empty, move its contents into .groove/tasks and remove the empty .beans directory.testing
Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.
data-ai
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
documentation
Document lessons, update rules/templates/docs. Use to capture learnings after review.
tools
Load groove workflow context into the conversation. Run at the start of every session.