daily-reminders
Skill2 starsChanged 39 days agoMITView on GitHub
Refresh an Apple Reminders "Today" list every morning from your calendar, deadlines and last night's leftovers, and keep a journal of what you ticked off. macOS only. Use when the user wants an automatic daily to-do list, a morning list refresh, or a Reminders list that rolls over unfinished tasks.
In this repository5 other files it gives its agents.
- image-prompt-directorSkill
- lfgSkill
- secretarySkill
- seedance-motion-directorSkill
- tech-company-analystSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 21
Run osascript scripts/rem-add.applescript "test" "" "" 5 once and allow the Reminders permission, then delete the test item.
≈ “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.
Files
daily-reminders
A small headless job: each morning Claude Code reads your calendar and notes, clears yesterday's
ticked items into a journal, and rebuilds one Reminders list called Today. Unfinished tasks
roll over, calendar events become 🕐 items with times, and a cap keeps the list short.
What is in the folder
scripts/— four AppleScripts that dump, add and clear Reminders,cal-today.js(reads macOS Calendar through EventKit), andrun-refresh.sh(runsclaude -pwith a locked-down tool list).templates/daily-prompt.txt— the instruction the job runs. Edit the bracketed parts: your deadlines file, standing daily items and notes to read.templates/launchd.plist.template— schedules it.
Set up
- Copy the folder to
~/.claude/skills/daily-reminders/and edittemplates/daily-prompt.txt. - Run
osascript scripts/rem-add.applescript "test" "" "" 5once and allow the Reminders permission, then delete the test item. Runosascript -l JavaScript scripts/cal-today.jsonce and allow the Calendar permission. - Dry run:
scripts/run-refresh.sh, then check the list and~/.claude/skills/daily-reminders/logs/. - Schedule: copy the plist template to
~/Library/LaunchAgents/, replaceYOURNAME, and runlaunchctl load ~/Library/LaunchAgents/<file>.plist.
Rules the job follows
- It may only touch the
Todaylist and append to one journal file. It never edits calendar events, sends messages or changes other files — the--allowedToolslist inrun-refresh.shenforces this, so keep it narrow. - Appends only; it never rewrites history.
- Unknown dates stay
TBC; it never invents one.
Limits
macOS only. The Mac must be awake (or wake via launchd) at the scheduled time. Headless runs use your own Claude Code login, so they count against your usage.
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
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.

