eod
Skill2 starsChanged 3 months agoMITView on GitHub
End-of-day close-out — summarize the day's operations into log.md and flag anything unfinished. Use when the user says "eod", "end of day", "close out the day", or "/eod".
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
- jcurbelo/agent-seedtheir own version, first seen Oct 17, 2026
- latuconsinafr/claude-code-configtheir own version, first seen Oct 13, 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
- jcurbelo/agent-seed★ 8same 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.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- lintSkill
- new-entitySkill
- onboardSkill
- session-handoffSkill
- session-startSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Ask: "anything learned today — a win or a mistake?" File wins in learnings.md, failures (with root cause + rule) in mistakes.md (schema §7).
- Very specific: line 20
If anything is unfinished, recommend running /session-handoff so tomorrow's session picks it up.
- Distinctive: line 22
Keep it under 10 bullets — this is a log, not a diary.
“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
End of Day
- Review what happened today: this session's operations + any log entries already written today.
- Append ONE consolidated block to
log.md:
## [YYYY-MM-DD] eod | <one-line day summary>
- <operation> → <result> (one bullet per meaningful thing)
- Unfinished: <what carries over>- Ask: "anything learned today — a win or a mistake?" File wins in
learnings.md, failures (with root cause + rule) inmistakes.md(schema §7). - If anything is unfinished, recommend running
/session-handoffso tomorrow's session picks it up. - Keep it under 10 bullets — this is a log, not a diary.
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.

