eod
Skill2 starsChanged 5 months agoMITView on GitHub
End of day — finalizes today's log, updates the task backlog, reconciles external trackers, and previews tomorrow's first priority.
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
- DINAKAR-S/company-ai-ostheir own version, first seen Aug 9, 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
- DINAKAR-S/company-ai-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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- control-plane/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- control-plane/CLAUDE.mdCLAUDE.md
- agentic-os-reference-syncSkill
- branch-cleanupSkill
- capture-triageSkill
- darwin-housekeepingSkill
- darwin-path-modeSkill
- decision-log-entrySkill
- expert-interview-guideSkill
- feedback-intakeSkill
- harness-onboardingSkill
- ingest-contentSkill
- meeting-to-work-itemsSkill
- memory-consolidateSkill
- morning-briefSkill
- os-bootstrap-extendSkill
- os-bootstrapSkill
- pr-reviewSkill
- scheduleSkill
- spec-cross-checkSkill
- ux-critiqueSkill
- weekly-retroSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Ask the principal (if not already told): what got done, what didn't, any decisions made, anything that changed.
- Very specific: line 22
Read today's control-plane/memory/daily/YYYY-MM-DD.md for what was logged through the day.
- Very specific: line 26
Update control-plane/memory/tasks/backlog.md: check off completed tasks, re-rank, add new ones, move stale P0s.
- Distinctive: line 27
Update status on any affected project files.
- Very specific: line 30
If anything today was clear evidence on a development objective (good or missed), note it in the daily log "Reflections" section and add to …
- Distinctive: line 33
If today is Friday and the weekly retro has not happened, offer to run it now: "Quer rodar o retro semanal antes de fechar?"
- Distinctive: line 43
Keep the recap short. The principal is done for the day.
- Distinctive: line 44
Do not re-explain everything in the log — just the highlights.
“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
Skill: eod
Purpose
Close the day cleanly so tomorrow starts with context, not archaeology.
Steps
- Collect what happened
- Ask the principal (if not already told): what got done, what didn't, any decisions made, anything that changed.
- Read today's
control-plane/memory/daily/YYYY-MM-DD.mdfor what was logged through the day.
- Delegate to
work-logger- Finalize today's daily log: fill "Done today", "Decisions made", "Carried to tomorrow" sections.
- Update
control-plane/memory/tasks/backlog.md: check off completed tasks, re-rank, add new ones, move stale P0s. - Update status on any affected project files.
- Development evidence capture
- If anything today was clear evidence on a development objective (good or missed), note it in the daily log "Reflections" section and add to the evidence log in
control-plane/memory/development/objectives.md. Keep it factual and specific.
- If anything today was clear evidence on a development objective (good or missed), note it in the daily log "Reflections" section and add to the evidence log in
- Friday trigger
- If today is Friday and the weekly retro has not happened, offer to run it now: "Quer rodar o retro semanal antes de fechar?"
- Deliver EOD recap (3-4 lines max)
- What got done
- What moved or changed
- Tomorrow's first priority
Rules
- Keep the recap short. The principal is done for the day.
- Do not re-explain everything in the log — just the highlights.
- Evidence capture for development objectives should be concrete: a specific moment, not a generalization.
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.