agentleFS
fabiohuebelfabiohuebel/claude-mac-bridge/skills/todos/SKILL.md

todos

Skill0 starsChanged 5 months agoMITView on GitHub

Pull, triage, prioritize, and manage your Apple Reminders from a Mac. Use to see your todos, decide what to work on next, add a reminder, or mark one done.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. JetBrains/thinkrail★ 7.9ksame name
    2. systemind-team/AICOO-Skills★ 35same name
    3. hcsum/dont-let-me★ 17same name
    4. protonium-labs/axiomcore-plugin★ 3same name
    5. caneva20/skills★ 2same 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never fabricate due dates.

    line 36
  2. Very specific:

    If list.sh ever feels too slow, a faster backend is reminders-cli (brew install keith/formulae/reminders-cli).

    line 37

“Common” is measured: kept by at least 6 in 10 of the 5 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

Todos (Apple Reminders)

Reads and writes Apple Reminders through the AppleScript helper scripts in this skill's scripts/ dir. Mac-only (Reminders syncs to the Mac via iCloud). Apple Reminders has no cloud connector, so this is the bridge.

Personalize first: these scripts take a list name as their first argument. Use the exact list names from Reminders.app's sidebar (e.g. Reminders, Work, Groceries). List names like Work below are placeholders.

On invocation

  1. Load all open reminders: bash ~/.claude/skills/todos/scripts/list.sh Reminders' AppleScript bridge is slow: this can take 30 to 60 seconds and may run in the background; if so, read the output file when it completes. Output lines are LIST ||| TITLE ||| DUE ||| PRIORITY (priority: 0 none, 1 high, 5 medium, 9 low; empty DUE means no due date).
  2. Present them grouped and prioritized, never a raw dump: cluster by theme/list, sort by due date, and explicitly flag overdue and no-due-date items.
  3. Then help the user act: recommend the single best next thing and break it into a concrete first step. For "what should I do today?", choose by due date + priority + lead time (how long the task takes to clear externally).

Adding a reminder

bash ~/.claude/skills/todos/scripts/add.sh "<list>" "<title>" [YYYY-MM-DD] [priority]

  • priority: 0 none, 1 high, 5 medium, 9 low. Due date optional (defaults to 09:00 that day).
  • Example: add.sh "Work" "Send invoice" 2026-07-01 1

Changing an existing reminder's due date / time

bash ~/.claude/skills/todos/scripts/set-due.sh "<list>" "<title substring>" "YYYY-MM-DD[ HH:MM]" [priority]

  • Edits the first OPEN matching reminder in place (no recreate). Supports a time of day: use this whenever a deadline has a specific time (e.g. "by 3pm"). Time defaults to 09:00; uses the Mac's local timezone.
  • add.sh cannot set a time (always 09:00) and has no edit mode, so for "give X a 3pm due date" or "move X to next week", prefer set-due.sh over complete+re-add.
  • Example: set-due.sh "Work" "Quarterly report" "2026-06-24 15:00" 1

Completing a reminder

bash ~/.claude/skills/todos/scripts/complete.sh "<list>" "<title substring>"

  • Marks the first OPEN reminder in that list whose name contains the substring; echoes what it completed (or "no match").

Guardrails

  • Confirm before bulk edits (adding many due dates, moving items between lists).
  • Never fabricate due dates; ask for the real deadline.
  • If list.sh ever feels too slow, a faster backend is reminders-cli (brew install keith/formulae/reminders-cli); offer it but do not require it.

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.