agentleFS
jcurbelojcurbelo/agent-seed/.claude/skills/eod/SKILL.md

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

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
  1. Very specific:

    Read today's todos/YYYY-MM-DD/todos.md

    line 9
  2. Distinctive:

    If integration agents are available:

    line 24
  3. Distinctive:

    Update today's todo file with final status

    line 32

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/eod - End of Day

Step 1: Review Today

  1. Read today's todos/YYYY-MM-DD/todos.md
  2. 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

  1. Identify carryover items (incomplete from today)
  2. Note any known priorities for tomorrow
  3. Update today's todo file with final status

Step 5: Commit

  1. Create branch: chore/eod-YYYY-MM-DD
  2. Stage changes to todos/ and memory/
  3. Commit: chore: eod YYYY-MM-DD
  4. Push and create PR (if gh is available)

Give a brief summary: "Today you completed X of Y items. Carrying over Z to tomorrow. Key learnings captured."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.