groove-utilities-task-list — Claude Code skill: list active tasks
Pulls active tasks from your configured backend and shows what is in progress, ready or blocked. Handy as a daily starting view.
npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a claude-codeWhat groove-utilities-task-list does
The skill reads the frontmatter of .groove/index.md to find tasks.backend and tasks.list_limit. Then it queries whichever source you configured and prints a grouped summary. In-progress tasks come first, then ready ones, then blocked ones with a note on what they are waiting for.
Three backends are wired in. With beans it runs skills/groove-utilities-task-list/scripts/list-tasks-by-priority.sh [LIMIT] and parses the output into status groups. With linear it fetches assigned, active issues through the linear CLI or MCP. With github it calls gh issue list --assignee @me --state open. If tasks.backend is none, you get a short no-op message and the skill exits.
When the backend CLI is missing or unreachable, the skill fails with an install hint — worth checking before you rely on the summary. Nothing gets modified along the way: the list is read-only.
What it helps with
- see what is in progress and what to pick up next
- tell blocked tasks apart from ready ones
- find out what a blocked task is waiting on
- collect open issues assigned to you in one call
- switch between task backends without changing habits
Example prompts for the agent
- list my active tasks
- what is in progress and what is blocked
- show today's task list
How to install groove-utilities-task-list
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a claude-code2Manually: put the files in place
~/.claude/skills/groove-utilities-task-list/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/groove-utilities-task-list/
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a codex2Manually: put the files in place
.agents/skills/groove-utilities-task-list/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a cursor2Manually: put the files in place
.cursor/skills/groove-utilities-task-list/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install andreadellacorte/groove groove-utilities-task-list2Manually: put the files in place
.github/skills/groove-utilities-task-list/SKILL.md1Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a gemini-cli2Platform CLI
gemini skills install https://github.com/andreadellacorte/groove --path skills/groove-utilities-task-listManually: put the files in place
.devin/skills/groove-utilities-task-list/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about groove-utilities-task-list
How do I install groove-utilities-task-list in Claude?
Run npx skills add andreadellacorte/groove --skill groove-utilities-task-list -a claude-code. The skill lands in ~/.claude/skills/groove-utilities-task-list/SKILL.md.
What does groove-utilities-task-list do?
It gathers active tasks from the configured backend and groups them by status: in-progress, ready, blocked. Blocked entries show what they are waiting on.
Which task backends are supported?
beans, linear and github. The backend is set in the frontmatter of .groove/index.md; with none the skill prints a message and exits.
Source text
SKILL.md · MIT
--- name: groove-utilities-task-list description: "List active tasks in the configured backend. Use to see current task status." license: MIT allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) AskUserQuestion metadata: author: andreadellacorte --- # groove-utilities-task-list ## Outcome A consolidated view of active, ready tasks from the configured backend is displayed to the user. Blocked and in-progress tasks are clearly distinguished. Output is suitable for daily start context. ## Acceptance Criteria - Tasks are shown grouped by status (in-progress, ready/todo, blocked) - Blocked tasks show what they are waiting on - In-progress tasks are listed first - Output is concise enough to scan at a glance ## Constraints - Read `.groove/index.md` frontmatter to determine `tasks.backend` and `tasks.list_limit` (default 15) - If `tasks.backend: none`, print a friendly no-op message and exit - Backend mappings: - `beans`: run `skills/groove-utilities-task-list/scripts/list-tasks-by-priority.sh [LIMIT]` with LIMIT from `tasks.list_limit` (or 15), then parse and format output (group by status: in-progress, todo, blocked) - `linear`: use linear CLI or MCP to fetch assigned, active issues - `github`: run `gh issue list --assignee @me --state open` - If backend CLI is not installed or unreachable, error clearly with install hint (see `/groove-utilities-task-install`) - Do not modify any tasks during list
© andreadellacorte · MIT · andreadellacorte/groove