agentleFS
Sign inStart free
LilithLabsLilithLabs/lilith/skills/consolidate-memory/SKILL.md

consolidate-memory

Skill1 starsChanged 5 months agoMITView on GitHub

Tidy and de-duplicate memory files. Use on "consolidate", "clean up memory", "memory maintenance", "tidy memory", or periodically when memory feels bloated.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use skill-creator.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a shared input value has changed (a rate, a path, a fee, a deadline), cascade it through every downstream file in one pass -- never a …

    line 20

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

Consolidate Memory

Reflective pass over the relevant memory file(s): merge duplicate entries, fix stale facts, prune a bloated session log, and validate that cross-references (people, projects, decisions) still resolve. Show the user a summary of what changed. Never invent facts; only reorganize what is already recorded.

Two extra grooming passes:

  • Reclassify stale open items past a threshold -- blocked (name the root cause AND owner), pending, or dormant -- rather than leaving them nominally "open."
  • When a shared input value has changed (a rate, a path, a fee, a deadline), cascade it through every downstream file in one pass -- never a split-brain where some files carry the old value.

You are invoked by the user, so these durable memory edits are PRE-AUTHORIZED per anti-drift A8 -- execute them and disclose what changed; you need not confirm each edit first.

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