agentleFS
vbonkvbonk/repo-template/.claude/skills/task-cleanup/SKILL.md

task-cleanup

Skill8 starsChanged 3 months agoMITView on GitHub

Archive or remove completed tasks from the task list. Use when task list grows large or to clean up after a project phase. Invoke with "/task-cleanup" or "clean up tasks". Triggers on "task-cleanup", "archive completed tasks", "clear completed tasks".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before handing off to another session

    line 15
  2. Distinctive:

    Keep pending and in_progress

    line 31
  3. Distinctive:

    Only archive completed tasks older than 24 hours

    line 34
  4. Distinctive:

    Keep recent completions for reference

    line 35
  5. Distinctive:

    Use when starting completely fresh

    line 39
  6. Distinctive:

    Use for housekeeping, not for hiding incomplete work

    line 76
  7. Distinctive:

    Consider running weekly or at project milestones

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Task Cleanup Skill

Manage task list hygiene by archiving or removing completed tasks.

When to Use

  • Task list has many completed tasks cluttering the view
  • End of a project phase or milestone
  • Starting fresh on a new focus area
  • Before handing off to another session

Execution Steps

1. Assess Current State

TaskList()
→ Count: pending, in_progress, completed
→ Identify tasks completed more than 24 hours ago

2. Present Options

Option A: Archive All Completed

  • Move all completed tasks to archive
  • Keep pending and in_progress

Option B: Archive Old Completed

  • Only archive completed tasks older than 24 hours
  • Keep recent completions for reference

Option C: Full Reset

  • Archive everything except in_progress
  • Use when starting completely fresh

3. Execute Cleanup

For each task to archive:

TaskUpdate({
  taskId: "<id>",
  metadata: { archived: true, archivedAt: "<ISO-8601>" }
})

Or mark completed with archive note:

TaskUpdate({
  taskId: "<id>",
  status: "completed",
  description: "[ARCHIVED] " + original_description
})

4. Report Results

## Task Cleanup Complete

**Before:** X total (Y pending, Z in_progress, W completed)
**After:** X total (Y pending, Z in_progress, 0 completed)
**Archived:** W tasks

Archive location: ~/.claude/tasks/{taskListId}/

Notes

  • Tasks are never truly deleted - metadata marks them archived
  • Archived tasks don't appear in normal TaskList output
  • Use for housekeeping, not for hiding incomplete work
  • Consider running weekly or at project milestones

Created: 2026-01-23 Part of: Task Management System v2.1.16

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.