plan-day
Skill0 starsChanged 5 months agoMITView on GitHub
One morning briefing that ties together your calendar, mail, and todos into a single organized plan for today. Read-only synthesis; only writes (blocks, flags, todos) after you approve.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Rajveerx11/skillstheir own version, first seen Oct 25, 2026
- shankerdhand/claude-second-braintheir own version, first seen Sep 10, 2026
- flurdy/agent-skillstheir own version, first seen Aug 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- flurdy/agent-skills★ 9same name
- Rajveerx11/skills★ 1same name
- shankerdhand/claude-second-brain★ 0same 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.
- agenda-syncSkill
- calendarSkill
- mailSkill
- todosSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
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
- Very specific: line 31
Add / date a todo: todos/scripts/add.sh / set-due.sh Propose one or two obvious moves.
- Very specific: line 35
Run it in the morning (or whenever you sit down).
- Very specific: line 38
Read-only until you approve a write.
- Distinctive: line 40
Do not fabricate times or deadlines.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Plan My Day (morning briefing)
The single command that ties together [[calendar]], [[mail]], [[todos]], and the gap-logic from [[agenda-sync]] into one organized plan for today. Read-only synthesis: it only writes (blocks, flags, todos) after you approve. Mac-only (Apple Mail/Calendar/Reminders live on the Mac). Requires the [[calendar]], [[mail]], and [[todos]] skills installed alongside it.
Routine (run in this order)
- Anchor to now.
date "+%A %Y-%m-%d %H:%M %Z": ground truth for the timeline and what is already past. - Kick off the slow todos pull first so it runs while you do the fast reads (it takes 30 to 60s and may background):
bash ~/.claude/skills/todos/scripts/list.sh - Today's calendar.
bash ~/.claude/skills/calendar/scripts/list.sh 0: build the timeline; dedupe duplicate-calendar entries; mark past vs ahead; note locations and any conflicts. - Mail triage.
bash ~/.claude/skills/mail/scripts/list.sh(default account; widen with another account name if asked). Classify into 🔴 Action / 🟠 FYI / ⚪️ Noise; keep only the Action items for the plan. Also tag which messages arrived overnight (since roughly 21:00 the previous evening, using the timestamps + the anchor time) for the overnight overview. - Todos for today. From the todos output, select: due today, overdue, high-priority (1), and anything tied to a today event. Ignore someday/low items unless asked.
Output: one organized plan
Present it as a tight briefing, not three raw dumps:
- 🌙 Overnight: a 1 to 2 line recap of what landed overnight: a count of new mail, who/what stands out (a real person, anything actionable), and an explicit "nothing urgent" if so. This is the first thing read.
- 📅 Today's timeline: events in order with times/locations, the next imminent thing called out, conflicts flagged.
- 🕳 Open gaps: each free block with length, and a concrete suggestion to fill it (deep work, the day's top todo, prep for the next meeting). Respect travel time between locations.
- ✅ Top priorities (ranked): merge deadlines-due-today + action mail + prep needs into a short ranked list (3 to 5 items).
- 📬 Needs a reply: the Action emails: who + what they want.
- 🎯 Start here: the single best first move given the current time.
Then offer to act (on approval only)
- Block a gap:
calendar/scripts/add.sh "" "<task>" "YYYY-MM-DD HH:MM" <min> - Flag an action email:
mail/scripts/flag.sh "<account>" "<subject>" on red - Add / date a todo:
todos/scripts/add.sh/set-due.shPropose one or two obvious moves; confirm before anything bulk.
Cadence
Run it in the morning (or whenever you sit down). Can be wrapped in /loop, but it is really a once-a-morning command, not a ticker. Pairs with [[agenda-sync]] for a deeper weekly (Friday) review.
Guardrails
- Read-only until you approve a write; never silently add/move/flag.
- The todos
list.shis slow and may background: read its output file when it completes before finalizing the plan. - Do not fabricate times or deadlines; surface noise as a count, never itemize newsletters.
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.