eod-summary
Skill2 starsChanged 24 days agoMITView on GitHub
End-of-day digest pulling today's wins, decisions, status changes, follow-ups, new artifacts, tomorrow's queue from session.jsonl + tasks + tracker files. User-invoked via /eod or auto-fire at end of day.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- advisorSkill
- agent-dispatchSkill
- arenaSkill
- audit-pypi-model-packageSkill
- branching-workflowSkill
- code-reviewSkill
- criticSkill
- cron-child-oauth-auditSkill
- daily-forestSkill
- deep-researchSkill
- diagnose-cron-timeoutSkill
- dreamingSkill
- filingSkill
- forest-synthesisSkill
- goalsSkill
- graph-hygieneSkill
- ideaSkill
- inline-tagsSkill
- intel-analyzerSkill
- longformSkill
- loop-experimentSkill
- loop-librarySkill
- meta-memory-reviewSkill
- office-hoursSkill
- open-loopsSkill
- plan-ceo-reviewSkill
- plan-design-reviewSkill
- prdSkill
- progressive-disclosureSkill
- reality-feedback-createSkill
- reality-review-weeklySkill
- recallSkill
- reconcile-extractionSkill
- redactSkill
- repo-auditSkill
- research-digestSkill
- review-gateSkill
- run-long-job-detachedSkill
- saveSkill
- scopeSkill
- self-auditSkill
- shadow-test-local-classifierSkill
- signal-scorerSkill
- skill-auditSkill
- skill-chainingSkill
- spawn-agent-in-tenantSkill
- spawn-tenantSkill
- split-log-rows-by-session-kindSkill
- subagent-delegationSkill
- telegram-dump-routerSkill
- telegram-reply-toolSkill
- verify-stackSkill
- wave-planSkill
- weekly-retroSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Task-list state: all tasks added/completed/changed today (compare against yesterday's snapshot if available)
- Very specific: line 61
When /eod fires, compile by:
- Distinctive: line 65
Read the personal follow-up tracker for state changes
- Very specific: line 87
progressive-disclosure: if EOD digest >1500 chars, auto-attach as .md instead of pasting
- Distinctive: line 94
Don't speculate or pad. If a section has nothing, skip it.
- Distinctive: line 95
Don't include yesterday's leftovers unless they materially advanced today.
- Very specific: line 102
Timezone: always your local timezone.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
EOD Auto-Summary
Pull today's firehose into one structured digest. Mobile-readable wrap.
Trigger
/eod: manual, any time. Compiles "today so far" snapshot.- Auto-fire end of day. NOT WIRED. Manual only.
Source data
The compiler pulls from these locations for today (date -d "today" +%Y-%m-%d):
logs/session.jsonl: events logged (commands, tasks, mode toggles, skills invoked, /save events): filter where ts starts with today's ISO date- Task-list state: all tasks added/completed/changed today (compare against yesterday's snapshot if available)
- Git status of
memory/: files modified/created today (memory writes durable across sessions) outputs/raw/andoutputs/reviewed/: files created today (work shipped)- A personal follow-up tracker (e.g.
workspace/personal/tracker.md): items submitted, status changes, follow-up due dates logs/errors.jsonl: errors logged today (surfaces unresolved or pending)
Format
🌙 EOD. Friday 2026-04-25
🎯 Shipped today (N):
- ...
📋 Decisions made (N):
- ...
🔄 Status changes (N):
- ...
⚠️ Open follow-ups (N):
- Due today: ...
- Due this week: ...
- Awaiting reply: ...
📝 New durable artifacts (N):
- memory/...: ...
- outputs/...: ...
- skills/...: ...
💤 Tomorrow's queue:
- ...
#meta #eodSections with zero items are omitted entirely (don't show empty headers).
Compilation (current: manual, model-driven)
When /eod fires, compile by:
- Filter today's
logs/session.jsonlevents (ts startswith today's ISO date) git status memory/→ new/modified files since 00:00 local- List files in
outputs/raw/andoutputs/reviewed/with mtime today - Read the personal follow-up tracker for state changes
- Pull task-list state (added/completed today)
- Render into the format above
- Save as
outputs/tg/eod-YYYY-MM-DD.md, send via the reply channel
Automation (parked): an eod_digest.py script would do steps 1-7 + auto-fire at end of day. NOT BUILT. Build trigger: after manual /eod proves stable for 5+ days.
Duration / size
Target: 800-1200 char digest. If the day was huge (a big ship day + two applications + a partner brief + infra patches), the digest can stretch to 1500. Beyond that → attach as .md per progressive-disclosure.
Cadence
- Any time during the day. Re-runs regenerate fresh from current state.
- Soft-cap one send per day. Mid-day re-runs save to
outputs/tg/only (no spam).
Why
50-100 scattered chat messages/day → one mobile-readable artifact. Closes the loop, kills "what did I do today" decay.
Composition with other skills
- progressive-disclosure: if EOD digest >1500 chars, auto-attach as
.mdinstead of pasting - inline-tags: EOD always tagged
#meta #eodfor retroactive search - /save: EOD does NOT replace
/save. /save extracts durable learnings to memory; /eod is a transient daily wrap. Both can run. - Stop-hook /save integration (parked): when the stop-hook runs at session end, /save fires; /eod is separate (could optionally chain at end of day, but not required).
Scope discipline
- Don't speculate or pad. If a section has nothing, skip it.
- Don't include yesterday's leftovers unless they materially advanced today.
- Open follow-ups: only those genuinely actionable tomorrow. "Awaiting a contact's reply Mon/Tue" = correct. "Maybe think about a side idea sometime" = skip.
- Decisions: include only consequential ones. "Picked B over A on a UI option" = skip. "Chose Path 1 over Path 2 for a boot-survival fix" = include.
Edge cases
- Empty day (no shipped, no decisions, no status changes): single-line digest
🌙 EOD. {date}: quiet day. {N} open follow-ups carry to tomorrow.Skip all empty sections, no padding. - Timezone: always your local timezone. Use
date -d "today" +%Y-%m-%dfor filtering. - Mid-day re-run: regenerate fresh from current state, do NOT diff against prior /eod output. Each run = snapshot.
- Partial source data (e.g. session.jsonl missing): note
⚠️ source: session.jsonl unavailablein the digest header, continue with what's readable. Don't fail the whole digest. - Tomorrow is weekend/OOO:
💤 Tomorrow's queuebecomes💤 Mon queue(next working day): don't pad with weekend filler unless something is genuinely due Sat/Sun.
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.

