study
Skill1 starsChanged 51 days agoMITView on GitHub
Daily study driver — reads due-card state and course progress, plans today's session (reviews → quiz → new material), runs it with the user, and writes the study log.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- halilural/imprimaturtheir own version, first seen Nov 8, 2026
- Sumit189/claude-codestheir own version, first seen Nov 1, 2026
- Slava-code/slava-stacktheir own version, first seen Oct 15, 2026
- gradigit/claude-skillstheir own version, first seen Oct 15, 2026
- JangInho/claude-skillstheir own version, first seen Oct 13, 2026
- pp6235024-bit/claude-skillstheir own version, first seen Oct 11, 2026
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- akashgit/remote-factory★ 74same name
- boston-harness-group/remote-factory★ 74same name
- mordor-forge/study-skill★ 46same name
- flc1125/skills★ 38same name
- alexiocassanifm/anthropic-certifications★ 36same name
- SugarMGP/study.skill★ 13same name
- WahyuS002/skills★ 5same name
- WindyITS/skills★ 5same name
- froster02/mini-Brain_skills★ 4same name
- matvej-melikhov/karpathy-llm-wiki★ 2same name
10 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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
0
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
- Very specific: line 32
Write log/study/YYYY-MM-DD.md from templates/study-log.md (planned vs.
“Common” is measured: kept by at least 6 in 10 of the 16 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
/study [--minutes <N>]
The daily loop. Read docs/pedagogy.md (session rules) and docs/vault-schema.md first. Vault: <vault>.
1. Gather state (read-only)
- Due cards: in every card file (definition, parsing recipe, and the local-day cutoff are at the bottom of
docs/vault-schema.md), grep<!--SR:and count per deck: due today/overdue, plus cards with no SR comment (= new). - Due problems: grep
retry afterincourses/*/problems/*.md; collect problems with retry date ≤ today. - Inbox: count pending items in
Inbox.md. - Courses: active course homes (
lessons_done/lessons_total,target_date); lessonsstatus/mastery/last_quizzed; quiz logs from the last 14 days; yesterday's study log carry-over.
2. Plan the session
Budget: --minutes or ~45 by default. Order per pedagogy: ⓪ process pending Inbox items (follow the /inbox procedure) ① due-card review in Obsidian (~1 min per 4 cards) ② retrieval work in the terminal — due problem re-attempts (follow the /problems --due procedure) and/or /quiz --weak on the weakest/stalest lessons ③ new material (next unread lesson, /learn --continue, or next /ingest chunk). Near a target_date (< 3 weeks), shift ③ toward cumulative interleaved quizzing instead of new content. Print the plan, e.g.:
① Obsidian: review 23 due cards (
qm-sakurai17,lagrangian6) — do this now, then come back. ②/quiz qm-sakurai --weak(L03 mastery 45, stale since Aug 12) — I'll run it here. ③ Read [[05 Perturbation Theory]] (~25 min), then mark it read.
3. Run it
Wait for the user to do the Obsidian review (ask for the plugin's end-of-review count as a sanity check). Run the quiz inline (follow the quiz skill's procedure). For reading items, confirm afterwards and set that lesson's status: read if it was unread (never downgrade a quizzed/mastered lesson).
4. Close out
Write log/study/YYYY-MM-DD.md from templates/study-log.md (planned vs. done, minutes, carry-over). If today's log already exists (second session), append a ## Session N block and add to minutes — never overwrite. Recompute course lessons_done if statuses changed. End with one line on tomorrow's priority.
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.