Skip to main content
affpapa.org
RU EN
skill CX Codex

groove-utilities-task-archive — Claude Code skill: archive tasks

Archives completed and scrapped tasks in the configured backend. Use it when you want to close a batch of finished work with a confirmation step.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add andreadellacorte/groove --skill groove-utilities-task-archive -a claude-code
Open on GitHub

What groove-utilities-task-archive does

The skill reads tasks.backend from .groove/index.md, identifies the configured service, and displays the tasks in scope. It asks for confirmation before changing anything, then reports how many tasks were archived.

For beans, it runs beans archive, which handles all completed or scrapped tasks rather than one selected task. With linear, filtered issues are archived through the CLI or MCP. With github, resolved issues are closed using gh issue close. A tasks.backend: none setting leaves the project unchanged.

The skill runs only after an explicit request. It does not start as part of the daily end routine, so unattended archiving is avoided.

What it helps with

  • archive completed tasks
  • remove scrapped tasks from the active queue
  • close resolved GitHub issues
  • review the archive scope before execution
  • report the number of archived tasks

Example prompts for the agent

  • Archive all completed and scrapped tasks.
  • Show me the archive scope, then run it after I confirm.
  • Read .groove/index.md and archive the tasks through the configured backend.

How to install groove-utilities-task-archive

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-task-archive -a claude-code

2Manually: put the files in place

~/.claude/skills/groove-utilities-task-archive/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/groove-utilities-task-archive/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about groove-utilities-task-archive

How do I install groove-utilities-task-archive in Claude Code?

Run npx skills add andreadellacorte/groove --skill groove-utilities-task-archive -a claude-code, then check ~/.claude/skills/groove-utilities-task-archive/SKILL.md.

What does groove-utilities-task-archive do?

It finds completed and scrapped tasks in the configured backend, shows the planned scope, waits for approval, and reports the archive count when finished.

Which backends can the skill use?

It uses beans archive for beans, the CLI or MCP for linear, and gh issue close for resolved github issues. With tasks.backend: none, it exits without changes.

Source text

SKILL.md · MIT 
---
name: groove-utilities-task-archive
description: "Archive a completed task in the configured backend."
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-archive

## Outcome

All completed and scrapped tasks are archived in the configured backend. The count of archived tasks is reported to the user.

## Acceptance Criteria

- All completed/scrapped tasks are moved to archived state in backend
- User is shown the scope of what will be archived and confirms before running
- Count of archived tasks is reported after completion

## Constraints

- Read `tasks.backend` from `.groove/index.md` to determine backend
- If `tasks.backend: none`, no-op with friendly message
- Always show user what will be archived and ask for confirmation before proceeding
- Never run automatically during daily end — only when user explicitly requests
- Backend mappings:
  - `beans`: `beans archive` (archives all completed/scrapped — no single-task option)
  - `linear`: mark filtered issues as archived via linear CLI or MCP
  - `github`: close resolved issues via `gh issue close`
- Report count of archived tasks after completion

© andreadellacorte · MIT · andreadellacorte/groove

Similar skills

All skills for Notes, tasks and projects →
find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. CX Codex +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. 1,219,756installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. 1,038,491installs grilling Matt Pocock Stress-test a plan, decision, or idea through structured rounds of questions. Use it when you need to expose assumptions before acting. 979,543installs teach Matt Pocock Turns the current directory into a learning workspace and keeps progress across sessions. Use it when learning needs to support a concrete goal in your project. 862,247installs

From the same set27

groove-work-audit This skill checks the current branch for gaps and assigns each finding an action. Use it before merging changes or reviewing a focused topic. CX Codex +1 540installs groove-work-compound This skill documents lessons after a review or planning session, updates project rules and templates, and traces root causes of mistakes. CX Codex +1 540installs groove-utilities-memory-log-git Writes a Git session summary to .groove/memory/git/. Use it when daily repository activity should stay in the project memory. CX Codex +1 538installs groove-work-exec This skill takes a finished implementation plan and writes the code, tests and docs for it, logging progress in your task backend. Use it once planning is done. CX Codex +1 536installs groove-utilities-memory-mistakes This skill turns an agent mistake into a tracked incident, fixes its cause, and records the lesson in project memory. Use it to stop repeat errors. CX Codex +1 529installs groove-admin-update Pulls the latest groove skills and applies pending migrations to your local groove state. Useful when a new release lands but your config and memory are still on the old one. CX Codex +1 528installs groove-work-doc Creates a reference document explaining how a codebase component or concept works. Use it when future agents or contributors need concrete project context. CX Codex +1 518installs groove-admin-cursor-hooks Registers groove's native Cursor hooks in .cursor/hooks.json: context re-priming after compaction, end-of-day reminders, a git commit buffer and managed-path protection. CX Codex +1 518installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor