groove-utilities-task-install
groove-utilities-task-install
Outcome
The configured task backend is installed and verified reachable. User is informed of what was installed and how to use it.
Acceptance Criteria
- Backend CLI is available in PATH after install
- User is shown a confirmation with the installed version or a reachability check
- No-op if
tasks.storage: none
Constraints
- Read
tasks.storagefrom.groove/index.mdto determine backend (if the key is still namedtasks.backendfrom an older config, treat it as the storage value). If the key is missing or invalid, you may pause and useAskUserQuestionso the user can choose a backend (beans,linear,github, ornone); then ensure.groove/index.mdis updated accordingly (via/groove-admin-configor an equivalent edit) before continuing. - If
tasks.storage: none, print friendly no-op message and exit - Installation source of truth: Do not embed OS-specific install commands in this skill. You must follow the official installation instructions from the upstream project for the user’s OS (read that page and run what it specifies). Link only:
beans: hmans/beans — Installation sectionlinear: schpet/linear-cli — install section (third-party CLI; not Linear’s hosted docs)github: GitHub CLI
- After the CLI is on PATH per those instructions, run a reachability check (
beans version,linear --version/linear --help, orgh version/gh auth statusas appropriate) - If the CLI is already installed before you start, report current version and skip fetching install instructions
- If
tasks.storage: beansand.beans.ymldoes not exist at git root:- Run
beans initto initialise the task store and generate.beans.ymlwith beans defaults - Derive
[PROJECT_PREFIX]from the git repo name (last path component ofgit remote get-url origin, stripped of.git, uppercased, non-alphanumeric stripped) — e.g.groove→GRV; fall back to the directory name if no remote - Update the
prefix:field in the generated.beans.ymlto the derived prefix (e.g.GRV-) - Set
path:in.beans.ymlto.groove/tasksso the task store lives under groove (aligned withgit.tasksand.groove/.gitignore). Create.groove/tasksif it does not exist. If the default.beansdirectory was created and is non-empty, move its contents into.groove/tasksand remove the empty.beansdirectory. - Report the path written and the prefix used
- Run
More from andreadellacorte/groove
pdf-to-markdown
[Document Processing] Convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR). Cross-platform.
257agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
251groove
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
248find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
245groove-utilities-memory-log-daily
Write the daily memory log entry. Use at end of day to record what happened.
235groove-daily-start
Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.
231