andreadellacorte

[Document Processing] Convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR). Cross-platform.

Create outcome spec (overview, decisions, steps, edge cases). Use $ARGUMENTS as spec topic if provided.

Evaluate output, identify lessons, decide accept/rework. Use after implementation.

Research codebase, write concrete implementation plan. Use after brainstorming.

Execute the implementation plan, track progress in the task backend. Use after planning.

Create a 'how does X work' documentation file for a codebase component or concept. Use $ARGUMENTS as the doc topic if provided.

Document lessons, update rules/templates/docs. Use to capture learnings after review.

Clarify scope through dialogue, surface key decisions and open questions. Use before planning.

Review current branch for blindspots; fix now / needs spec / create issues.

Update an existing task in the configured backend.

List active tasks in the configured backend. Use to see current task status.

Set up task backend and configuration.

Check task backend health and connectivity.

Create a new task in the configured backend.

Configure task backend settings interactively.

Archive a completed task in the configured backend.

Analyse task status and distribution across the configured backend.

Quantified compound-loop dashboard: lessons captured vs graduated, adherence streaks, and task velocity. Use to see whether the workflow is actually compounding.

Load groove workflow context into the conversation. Run at the start of every session.

Generate a GROOVE.md onboarding guide for contributors to a groove-enabled project. Explains the compound loop, commands, and conventions.

Analyse workflow trends: session ratings, recurring mistakes, and learnings over a period. Use for weekly or monthly reflection.

Capture and resolve deferred items from a session ('we'll come back to that'). Use $ARGUMENTS as the promise text, or --list / --resolve N.

Log a workflow mistake, fix its root cause, and graduate the lesson to learned memory. Use when the agent makes an error you want to prevent recurring.

Roll up the weekly memory log from daily entries.

Roll up the monthly memory log from weekly entries.

Record git activity summary in memory log.

Write the daily memory log entry. Use at end of day to record what happened.

Set up memory backend and configuration.

Graduate a workflow insight from learned/<topic>.md into AGENTS.md as a permanent constraint. Use when a lesson is stable enough to apply to every future session.

Check memory backend health and configuration.

Check if a newer version of groove is available on GitHub.

Browse and review open learning PRs in the configured groovebook repo. Use to participate in the shared groove commons.

Publish a workflow learning to the groovebook shared commons as a GitHub PR. Use after groove-work-compound when a learning is worth sharing.

Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.

End the workday: write memory, analyse tasks, run end hook. Use when wrapping up the day.

Pull latest groove skills and apply pending migrations to local groove state.

Install groove backends, companions, and AGENTS.md bootstrap. Run once per repo.

Display all groove skills and commands with live config values.

Run all groove health checks: config, backends, companions, AGENTS.md.

Install groove's Cursor native hooks into .cursor/hooks.json. Enables compaction-safe re-priming, session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.

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

Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.

Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.

Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.

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.

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.