agentleFS
Sign inStart free
not-manunot-manu/skills/update-todos/SKILL.md

update-todos

Skill1 starsChanged 4 months agoMITView on GitHub

Update the project's TODO.md by checking off completed tasks and moving them under the **done** section. Use this skill whenever the user asks to update todos, mark a task done, move completed items to done, tick off a todo, or clean up TODO.md after finishing work — even when they don't explicitly mention the file. Also trigger on phrases like "/update-todos", "log that as done", "move this to done", or "todo bookkeeping".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jcurbelo/agent-seed★ 8same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep TODO.md tidy after work is finished.

    line 8
  2. Very specific:

    Read TODO.md at the repo root (or the path the user names).

    line 12
  3. Distinctive:

    Remove it from its current location in the open list.

    line 15
  4. Distinctive:

    Don't invent tasks, don't reword open items, don't reorder unrelated lines.

    line 22
  5. Very specific:

    If there's no done section yet, create one just below the open list.

    line 23
  6. Distinctive:

    If nothing in the conversation maps to an open todo, say so instead of forcing a move.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

update-todos

Keep TODO.md tidy after work is finished. Minimal, mechanical.

What to do

  1. Read TODO.md at the repo root (or the path the user names).
  2. Identify which open - [ ] items the recent conversation actually completed. If it's ambiguous, ask the user which ones to move — don't guess.
  3. For each completed item:
    • Remove it from its current location in the open list.
    • Append it to the **done** section as - [x] <text>. No notes, no explanations, no trailing prose — the title alone. The user can read the git log for the why.
  4. Preserve the rest of the file verbatim — section headers, blank lines, ordering of untouched items, indentation style.

Notes

  • The **done** section is the archive. New entries go at the bottom of it.
  • Don't invent tasks, don't reword open items, don't reorder unrelated lines.
  • If there's no **done** section yet, create one just below the open list.
  • If nothing in the conversation maps to an open todo, say so instead of forcing a move.

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.

Check your setup, free