today
Skill217 starsChanged 8 months agoMITView on GitHub
Generate daily plan from due tasks and active projects. Part of chief-of-staff vault system.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- yourbeckett/beckett-for-claudetheir own version, first seen Nov 1, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- dymchenkko/claude-study-agenttheir own version, first seen Oct 20, 2026
- ClarvAI/job-search-hqtheir own version, first seen Oct 15, 2026
- DavoDC/claude-playbooktheir own version, first seen Oct 13, 2026
- flowing-abyss/obsidian-vault-skillstheir own version, first seen Sep 19, 2026
Used with
Projects with it also use update and start.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
AnthropicSkillstart
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- kv0906/pm-kit★ 138same name
- aleksander-dytko/ai-pm-workspace★ 34same name
- jexchan/dailyup-second-brain-starter★ 33same name
- flowing-abyss/obsidian-vault-skills★ 9same name
- flurdy/agent-skills★ 9same name
- ARCASSystems/FounderOS★ 7same name
- SidU/claude-today-skill★ 4same name
- conorbronsdon/agent-workspace★ 2same name
- dymchenkko/claude-study-agent★ 2same name
- serhii12/vault-os★ 2same name
8 more not listed
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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-farmerSkill
- daily-reviewSkill
- delegate-taskSkill
- farmSkill
- historySkill
- newSkill
- start-second-brainSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Check if daily/YYYY-MM-DD.md exists - if so, read it first
- Distinctive: line 16
If no tasks found for today/overdue, grep for dates through end of week
- Distinctive: line 17
If still none, grep to find the next earliest due date
- Distinctive: line 18
Read only the matching task files
- Very specific: line 20
Run git log --since="midnight" --grep="cos:" --oneline for today's activity
- Very specific: line 21
Create or update daily/YYYY-MM-DD.md
- Very specific: line 25
All tasks have due: YYYY-MM-DD in frontmatter.
- Distinctive: line 38
Only read files returned by grep.
- Distinctive: line 42
When the daily file already exists:
- Very specific: line 43
Keep any [x] completed items as-is
- Distinctive: line 44
Keep any manually added items (not from vault tasks)
- Distinctive: line 45
Add new tasks from vault that aren't already present
“Common” is measured: kept by at least 6 in 10 of the 15 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
/today - Daily Planning
Generate today's plan from vault contents.
Steps
- Check if
daily/YYYY-MM-DD.mdexists - if so, read it first - Find tasks by due date using grep (never glob all tasks):
- Grep for
due: YYYY-MM-DD(today's date) → Due Today - Grep for dates before today → Overdue
- If no tasks found for today/overdue, grep for dates through end of week
- If still none, grep to find the next earliest due date
- Grep for
- Read only the matching task files
- Grep
projects/*.mdforstatus: active, read those files - Run
git log --since="midnight" --grep="cos:" --onelinefor today's activity - Create or update
daily/YYYY-MM-DD.md
Task Discovery (grep-first approach)
All tasks have due: YYYY-MM-DD in frontmatter. Use grep to find relevant tasks efficiently:
# Today's tasks (replace with actual date)
grep -l "due: 2026-01-23" tasks/*.md
# Overdue: grep for each date before today, or use date range pattern
grep -l "due: 2026-01-2[0-2]" tasks/*.md # dates 20-22 if today is 23rd
# This week: grep for dates through end of week
grep -l "due: 2026-01-2[3-9]" tasks/*.md # adjust pattern for weekOnly read files returned by grep. Never glob and read all task files.
Update Behavior
When the daily file already exists:
- Keep any
[x]completed items as-is - Keep any manually added items (not from vault tasks)
- Add new tasks from vault that aren't already present
- Refresh the Recent Activity section with latest git log
- Preserve any custom sections added by user
Output Format
---
type: daily
date: YYYY-MM-DD
---
## Due Today
- [ ] Task items from tasks/ with today's due date
## Overdue
- [ ] Tasks past due (X days overdue)
## Active Projects
- Project Name (next: next action from file)
## Recent Activity
- Items from git logDoes 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.

