eod
Skill8 starsChanged 8 months agoMITView on GitHub
End of day wrap-up. Review completed work, capture learnings, update memory, prep tomorrow.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Nicolas-Rigaudy/cr-0wtheir own version, first seen Nov 8, 2026
- sschemel/second-brain-startertheir own version, first seen Oct 30, 2026
- latuconsinafr/claude-code-configtheir own version, first seen Oct 13, 2026
- DINAKAR-S/company-ai-ostheir own version, first seen Aug 9, 2026
- DScardini91/agentic-ostheir own version, first seen Jun 26, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- DINAKAR-S/company-ai-os★ 2same name
- DScardini91/agentic-os★ 2same name
- Nicolas-Rigaudy/cr-0w★ 1same name
- latuconsinafr/claude-code-config★ 0same name
- sschemel/second-brain-starter★ 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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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 9
Read today's todos/YYYY-MM-DD/todos.md
- Distinctive: line 24
If integration agents are available:
- Distinctive: line 32
Update today's todo file with final status
“Common” is measured: kept by at least 6 in 10 of the 5 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
/eod - End of Day
Step 1: Review Today
- Read today's
todos/YYYY-MM-DD/todos.md - Summarize: what got done, what didn't, what's blocked
Step 2: Capture Learnings
Launch the reflection agent to review the current session:
- New preferences or corrections the user made
- Technical insights worth remembering
- Patterns that have occurred 3+ times
- Gaps in agents or context that need fixing
The reflection agent updates memory/ files directly.
Step 3: Check for Late Activity
If integration agents are available:
- Scan for any late-day messages or updates that need attention tomorrow
- Note anything that came in after the last todo update
Step 4: Prep Tomorrow
- Identify carryover items (incomplete from today)
- Note any known priorities for tomorrow
- Update today's todo file with final status
Step 5: Commit
- Create branch:
chore/eod-YYYY-MM-DD - Stage changes to
todos/andmemory/ - Commit:
chore: eod YYYY-MM-DD - Push and create PR (if
ghis available)
Give a brief summary: "Today you completed X of Y items. Carrying over Z to tomorrow. Key learnings captured."
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.

