agentleFS
chrisblattmanchrisblattman/claudeblattman/skills/todo-add/SKILL.md

todo-add

Skill479 starsChanged 22 days agoMITView on GitHub

Add a task to the appropriate configured to-do list while checking for duplicates.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    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:

    Add a new to-do item to the correct list with duplicate checking.

    line 9
  2. Distinctive:

    If not provided by the user, ask:

    line 15
  3. Distinctive:

    Read the target TODO file and scan for similar items.

    line 40
  4. Distinctive:

    If potential duplicate found:

    line 45
  5. Distinctive:

    Update the "Last updated" date in the file header.

    line 66
  6. Distinctive:

    Add more lists by creating additional todo files and adding them here.

    line 81
  7. Distinctive:

    If the user specifies a list directly, skip the routing suggestion

    line 95
  8. Distinctive:

    If the user specifies priority, use it.

    line 96
  9. Distinctive:

    Priority mapping: If your todo files use different section names (e.g., "Active" / "Up Next" / "Someday" instead of "High" / "Medium" / …

    line 108
  10. Distinctive:

    Single vs. multi-list: If you only use one todo file, you can simplify this skill by removing the routing logic in Step 2 entirely and …

    line 115

≈ “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

Add To-Do Item

v1.1 — Adapted for public use

Add a new to-do item to the correct list with duplicate checking.

Instructions

1. Get the item details

If not provided by the user, ask:

  • What's the task? (brief description)
  • Any additional context?

2. Determine the correct list

Based on the item content, suggest the appropriate list using the routing table below. This table is an example — customize it to match your own lists and keywords.

Keywords/TopicsSuggested List
config, settings, infrastructure, setup, toolsMain
email, calendar, briefing, schedulingWork

Present your suggestion:

This sounds like a [Main/Work] item because [reason].

Suggested list: ~/Documents/todo.md
Priority: [High/Medium/Low]

Is this correct, or should it go elsewhere?

3. Check for duplicates

Read the target TODO file and scan for similar items. Check for:

  • Same keywords in item titles
  • Related tasks that might overlap
  • Items that could be expanded instead of duplicated

If potential duplicate found:

Potential duplicate detected:

Existing item: "[item title]"
Location: [file path], [priority level]

Options:
1. Add anyway (they're different enough)
2. Update the existing item instead
3. Cancel

4. Add the item

Once confirmed, add to the appropriate section with this format:

- [ ] **[Item title]**
  - [Context/details if provided]

Update the "Last updated" date in the file header.

5. Confirm

Added to [list name]:
  - [ ] **[Item title]**

Priority: [High/Medium/Low]

File Locations

  • Main: ~/Documents/todo.md

Add more lists by creating additional todo files and adding them here. For example:

  • Work: ~/Documents/todo-work.md
  • Personal: ~/Documents/todo-personal.md

Priority Definitions

PriorityWhen to use
HighBlocking progress, causing problems, or time-sensitive
MediumWould improve things but not blocking
LowNice to have, someday

Notes

  • If the user specifies a list directly, skip the routing suggestion
  • If the user specifies priority, use it; otherwise suggest based on urgency cues

Customization Points

To set up this skill for your workflow:

  1. File locations: Edit the "File Locations" section to point to your actual todo files. You can use any number of lists — one file per list works well.
  2. Keyword routing table: Edit the table in Step 2 to reflect your own categories. For example, if you have a "Research" list, add a row like | papers, data, analysis, literature | **Research** |.
  3. Priority mapping: If your todo files use different section names (e.g., "Active" / "Up Next" / "Someday" instead of "High" / "Medium" / "Low"), add a mapping note. For example:
    High → Active
    Medium → Up Next
    Low → Someday
  4. Single vs. multi-list: If you only use one todo file, you can simplify this skill by removing the routing logic in Step 2 entirely and hardcoding the single file path.
  5. Item format: The default format uses - [ ] **Title** with indented context. Adjust to match your existing todo file format (e.g., plain - [ ] Title or numbered lists).

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.