consolidate-memory
Skill3 starsChanged 33 days agoMITView on GitHub
Use when a plan finishes or agent memories have piled up. Merges agent project memories and notepad learnings into the project's auto-memory index.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- invergent-ai/surogatestheir own version, first seen Oct 13, 2026
- GeekFamilyCorp/TricorderKittheir own version, first seen Oct 13, 2026
- jesusalgartrainer/claude-skillstheir own version, first seen Oct 13, 2026
- docvinum/agent-skillstheir own version, first seen Sep 2, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- LilithLabs/liliththeir own version, first seen Jun 20, 2026
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.
SentrySkillskill-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
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- GeekFamilyCorp/TricorderKit★ 32same name
- invergent-ai/surogates★ 28same name
- Hassaan146/claude-skills★ 18same name
- thtskaran/claude-skills★ 18same name
- csiddhant796-blip/claude-skills-collection★ 2same name
- LilithLabs/lilith★ 1same name
- docvinum/agent-skills★ 0same name
- jesusalgartrainer/claude-skills★ 0same name
- Myra-Agents/skills★ 0same name
- talgacapri/pm-os★ 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hooks/AGENTS.mdAGENTS.md
- opencode/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- servers/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- statusline/AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- analyzerSkill
- build-fixerSkill
- debuggingSkill
- github-triageSkill
- git-masterSkill
- handoffSkill
- init-deepSkill
- omca-setupSkill
- planSkill
- refactorSkill
- remove-ai-slopsSkill
- reviewerSkill
- start-workSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
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
- Distinctive: line 13
Read agent memory files at both scopes if accessible:
- Very specific: line 17
Update the project's auto-memory index, ~/.claude/projects/<project>/memory/MEMORY.md (or MEMORY.md under the autoMemoryDirectory setting …
- Distinctive: line 22
Only persist patterns confirmed across multiple interactions
- Distinctive: line 23
Remove session-specific context (in-progress tasks, temporary state)
“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.
Files
Consolidate memory
Consolidate session knowledge into persistent memory.
Steps
notepad_read(plan_name): all sections for active plan; load it if needed:ToolSearch({query: "select:mcp__plugin_oh-my-claudeagent_omca__notepad_read", max_results: 1})- Read agent memory files at both scopes if accessible:
- user scope:
~/.claude/agent-memory/*/MEMORY.md - project scope:
.claude/agent-memory/*/MEMORY.md(platform writes project memories here, resolving from the project root)
- user scope:
- Identify learnings, patterns, decisions worth preserving
- Update the project's auto-memory index,
~/.claude/projects/<project>/memory/MEMORY.md(orMEMORY.mdunder theautoMemoryDirectorysetting when set): concise, deduplicated - Note what was kept vs too session-specific
Guidelines
- Only persist patterns confirmed across multiple interactions
- Remove session-specific context (in-progress tasks, temporary state)
- Organize by topic, not chronologically
- MEMORY.md loads first 200 lines or 25KB per session. Consolidate when approaching limits.
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.

