today
Skill2 starsChanged 7 days agoMITView on GitHub
Start a daily ~15-minute study session - due reviews first, then the next topic with micro-tasks. Use when the user says "today", "let's study", "daily session" or opens without a specific request.
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
- ClarvAI/job-search-hqtheir own version, first seen Oct 15, 2026
- DavoDC/claude-playbooktheir own version, first seen Oct 13, 2026
- bradautomates/second-braintheir own version, first seen Oct 9, 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
- bradautomates/second-brain★ 217same name
- 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
- 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- Example-Subject/CLAUDE.mdCLAUDE.md
- _template/CLAUDE.mdCLAUDE.md
- examSkill
- ingestSkill
- learnSkill
- quizSkill
- reviewSkill
- setupSkill
- statusSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Run ~/Study/.tools/study plan --json (add the subject name if I gave one, and --minutes N if I gave minutes: N / 5 picks, at least 1, at …
- Very specific: line 18
todohas picks: use the pick flow below. - Distinctive: line 19
A subject was named and has no picks today: run the classic flow below for that subject.
- Very specific: line 27
Read that pick's subject files: CLAUDE.md, progress.md, mistakes.md, the latest file in sessions/.
- Very specific: line 28
If it has a Diagrams entry, diagram tasks follow the Diagrams rules in ~/Study/CLAUDE.md.
- Distinctive: line 29
Do the pick (~5 min), following the teaching rules:
- Very specific: line 43
Read the subject's CLAUDE.md, progress.md, mistakes.md and the latest file in sessions/.
- Distinctive: line 44
If its reviews are paused, skip the warm-up.
- Very specific: line 50
Update progress.md, mistakes.md, write sessions/<today>.md (append if it exists) and run study log.
- Very specific: line 53
If syllabus.md has no topics yet, tell me to run /ingest <subject> first (or offer to run it).
“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
Daily session (default 15 min = 3 picks of ~5 min)
Today's plan is shared with the Plan tab of study gui, so both always show the same picks.
- Run
~/Study/.tools/study plan --json(add the subject name if I gave one, and--minutes Nif I gave minutes: N / 5 picks, at least 1, at most 3).todois the list of unfinished picks for this session,pausedlists subjects whose reviews are paused. - Decide the flow:
- A paused subject named in the argument: say its reviews are paused and ask whether to resume
(replace its
- **Reviews:**line with- **Reviews:** resumed <today>). Don't start until I confirm; if I say no, offer the picks of other subjects instead. todohas picks: use the pick flow below.- A subject was named and has no picks today: run the classic flow below for that subject.
- No picks left (all done, or the plan is empty): say so in one line. Offer the classic flow for the non-paused subject with the most overdue topics. If every subject is paused, say that and offer to resume one.
- A paused subject named in the argument: say its reviews are paused and ask whether to resume
(replace its
- Show the plan in 3 lines max, one per pick:
1. PRI · Association class — 2 open mistakes (review).
Pick flow (one pick at a time, in order, across subjects)
For each pick:
- Read that pick's subject files:
CLAUDE.md,progress.md,mistakes.md, the latest file insessions/. If it has a Diagrams entry, diagram tasks follow the Diagrams rules in~/Study/CLAUDE.md. - Do the pick (~5 min), following the teaching rules:
review: up to 3 short recall questions on that topic only, unfixed mistakes first (as in /review).lesson: start the topic as in /learn, small: one idea, one micro-task, grade, adapt.drawing: one drawing task on that topic in draw.io (the chat answers were right, the diagram slipped).
- Save right away, before moving on:
progress.md,mistakes.md, append tosessions/<today>.mdof that pick's subject, andstudy log(Event log rule in~/Study/CLAUDE.md). A pick counts as done when its topic's Last studied is today, so stopping early loses nothing.
Finish (≈2 min, once at the end): one exam-style question on the finished pick where I scored best. Log it like the rest (it is a recall on that topic). End with: what improved, what's due tomorrow, and a one-line suggestion for next time.
Classic flow (one subject, no picks)
- Read the subject's
CLAUDE.md,progress.md,mistakes.mdand the latest file insessions/. If its reviews are paused, skip the warm-up. - Plan in 3 lines max, e.g.
Warm-up: 3 reviews · Main: <topic> · Finish: 1 exam-style question. - Warm-up (≈3 min): up to 3 due items (Next review ≤ today), unfixed mistakes first. One question at a time.
- Main (≈10 min): continue the topic from the last session log, or the next unstarted topic in
syllabus.md. Follow the teaching rules in~/Study/CLAUDE.md: explain small → micro-task → grade → adapt. - Finish (≈2 min): one exam-style question on today's main topic.
- Update
progress.md,mistakes.md, writesessions/<today>.md(append if it exists) and runstudy log. End with: what improved, what's due tomorrow, and a one-line suggestion for next time.
If syllabus.md has no topics yet, tell me to run /ingest <subject> first (or offer to run it).
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.

