agentleFS
jaredhhawkjaredhhawk/claude-skills/skills/tasks/SKILL.md

tasks

Skill0 starsChanged 8 months agoMITView on GitHub

Review, format, and clean up the task inbox. Auto-adds checkboxes, shows summary, and archives completed tasks.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use send-user-message, tinyagi-admin and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Maliot100XSkill

    send-user-message

    Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.

    Also in 4 projects that use this

  • jlia0Skill

    tinyagi-admin

    Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.

    Also in 3 projects that use this

  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 6 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • anyprotoSkill

    skills-manager

    Context-aware routing to skills and hooks management. Use when troubleshooting skill activation, fine-tuning keywords, or managing the automated documentation system.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: "Archive X completed tasks?

    line 41
  2. Very specific:

    Add under the current month's ## YYYY-MM section (create if needed)

    line 45
  3. Very specific:

    Add [archived:: YYYY-MM-DD] to each task

    line 46
  4. Very specific:

    Remove #today tag from archived tasks (no longer relevant)

    line 47
  5. Very specific:

    Remove the completed tasks from 01_TASKS.md

    line 48
  6. Distinctive:

    If any lines look like standalone URLs (not part of a task), suggest:

    line 51
  7. Very specific:

    If yes: Move to 01_Inbox/00_EXPLORE.md under ## Queue

    line 55
  8. Distinctive:

    When archiving, add tasks under the appropriate month section.

    line 103

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “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

/tasks - Task Inbox Cleanup

You are helping the user manage their task inbox at 01_Inbox/01_TASKS.md.

Files

  • Task Inbox: 01_Inbox/01_TASKS.md - Active/open tasks
  • Archive: 05_Archives/Completed Tasks.md - Completed tasks moved here

Behavior

  1. Read the task file at 01_Inbox/01_TASKS.md
  2. Auto-fix formatting - Fix lines that look like tasks but have formatting issues:

    • Lines starting with - but no [ ] → add checkbox: - [ ]
    • Plain text lines that look like tasks (not URLs, headers, blank, or dataview) → add - [ ]
    • Normalize spacing (remove double spaces, fix indentation)

    Skip these (don't add checkboxes):

    • Lines that are just URLs (start with http or are on their own line)
    • Blank lines
    • Headers (lines starting with #)
    • Dataview code blocks (between ```dataview and ```)
    • Lines that already have - [ ] or - [x]
    • The frontmatter block
    • Lines starting with Related: or Nav:
  3. Show summary:
    Task Inbox Summary:
    - X open tasks (Y tagged #today)
    - Z completed tasks ready to archive
  4. Archive completed tasks (if any [x] tasks exist):
    • Ask: "Archive X completed tasks? (y/n)"
    • If yes:
      1. Read 05_Archives/Completed Tasks.md
      2. Move completed tasks from inbox to archive file
      3. Add under the current month's ## YYYY-MM section (create if needed)
      4. Add [archived:: YYYY-MM-DD] to each task
      5. Remove #today tag from archived tasks (no longer relevant)
      6. Remove the completed tasks from 01_TASKS.md
  5. Check for misplaced items:
    • If any lines look like standalone URLs (not part of a task), suggest:
      "Found X URLs that might belong in your Explore queue. Move them? (y/n)"
    • If yes: Move to 01_Inbox/00_EXPLORE.md under ## Queue
  6. Save changes to both files after operations

Auto-Checkbox Logic

Apply checkboxes intelligently:

BEFORE:                          AFTER:
- Buy groceries                  - [ ] Buy groceries
- [ ] Already formatted          - [ ] Already formatted
- [x] Done task                  - [x] Done task
Call mom                         - [ ] Call mom
https://example.com              https://example.com (skip - URL)
## Header                        ## Header (skip - header)

Archive File Structure

The archive file is organized by month:

---
Domain: "[[D - Career & Job Search]]"
tags:
  - archive
  - tasks
created: 2026-02-05
---
Related: [[01_Inbox/01_TASKS|Task Inbox]]

# Completed Tasks

Archive of completed tasks from the task inbox.

---

## 2026-02

- [x] Task completed in Feb [archived:: 2026-02-05]
- [x] Another task [archived:: 2026-02-10]

## 2026-01

- [x] Task from January [archived:: 2026-01-15]

When archiving, add tasks under the appropriate month section. Create new month sections as needed, keeping them in reverse chronological order (newest at top).

Conversation Style

  • Brief, action-oriented
  • Show counts clearly
  • Don't over-explain
  • Confirm changes made at the end

Example Interaction

Claude: Task inbox reviewed.

Fixed formatting:
- Added checkboxes to 3 items

Summary:
- 8 open tasks (3 tagged #today)
- 2 completed tasks ready to archive

Archive 2 completed tasks? (y/n)

User: y

Claude: Done. Moved 2 tasks to Completed Tasks archive.

Your open tasks:
1. Change batteries in alarm #today
2. Schedule Colonoscopy #today
3. LabCorp bloodwork #today
...

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.