agentleFS
Sign inStart free
bastegmanbastegman/OpenClaude/.claude/skills/memory-flush/SKILL.md

memory-flush

Skill0 starsChanged 4 months agoMITView on GitHub

Daily memory maintenance. Close yesterday's daily with a summary, create today's, update affected project memories and MEMORY.md if there is anything significant. Invoke manually or via a scheduled task.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. aaronjmars/aeon★ 789same name
    2. aeonfun/aeon★ 789same name
    3. aaronjmars/miroshark-aeon★ 20same name
    4. MiroShark/miroshark-aeon★ 20same 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 repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 8

    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
  1. Distinctive:

    Run the daily maintenance of the system's memory.

    line 8
  2. Very specific:

    Read memory/daily/YYYY-MM-DD.md for yesterday

    line 13
  3. Distinctive:

    Add a summary at the end if it doesn't have one

    line 14
  4. Very specific:

    Create memory/daily/YYYY-MM-DD.md with the template:

    line 18
  5. Very specific:

    Update each relevant memory/projects/*.md

    line 39
  6. Distinctive:

    Only if there is something significant (new decision, new project, priority change)

    line 42
  7. Distinctive:

    Don't update out of routine — only for real content

    line 43
  8. Distinctive:

    No stale information left unmarked

    line 48
  9. Distinctive:

    If in doubt about what was significant, include it

    line 53
  10. Distinctive:

    Never delete information — archive or mark as stale

    line 54
  11. Distinctive:

    Run in under 2 minutes

    line 55

“Common” is measured: kept by at least 6 in 10 of the 4 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

Memory Flush — Daily Cut

Run the daily maintenance of the system's memory.

Process

  1. Close yesterday's daily:
    • Read memory/daily/YYYY-MM-DD.md for yesterday
    • Add a summary at the end if it doesn't have one
    • Mark as closed
  2. Create today's daily:
    • Create memory/daily/YYYY-MM-DD.md with the template:
      # YYYY-MM-DD

## Priorities
- [ ]
- [ ]
- [ ]

## Work done


## Decisions made


## Pending for tomorrow
  3. Update project memories:
    • Review which projects were touched yesterday
    • Update each relevant memory/projects/*.md
  4. Update MEMORY.md:
    • Only if there is something significant (new decision, new project, priority change)
    • Don't update out of routine — only for real content
  5. Check consistency:
    • MEMORY.md does not contradict recent dailies
    • Active projects reflect real state
    • No stale information left unmarked

Rules

  • Silent maintenance — don't message the user
  • If in doubt about what was significant, include it
  • Never delete information — archive or mark as stale
  • Run in under 2 minutes

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.

Check your setup, free