swarm-memory
Skill2 starsChanged 7 months agoApache-2.0View on GitHub
Git-based multi-agent memory synchronization. Activated when managing agent memory files, syncing memories across devices, or organizing long-term knowledge.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- chadixearth/graphylooptheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- chadixearth/graphyloop★ 3same 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 repository4 other files it gives its agents.
- migrate-openclawSkill
- persona-managerSkill
- soul-rollbackSkill
- soulscanSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 31
Always commit memory changes with descriptive messages
- Distinctive: line 32
Search memory before answering questions about prior work
≈ “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
Swarm Memory — Git-Based Memory Sync
Manage structured memory files that persist across sessions and sync across devices via Git.
When to activate
- User asks about agent memory, knowledge, or recall
- User mentions MEMORY.md, memory files, or daily logs
- User wants to sync, search, or organize agent memories
- Memory conflicts or merge issues arise
Memory architecture (4-Tier)
- T0 (Identity): SOUL.md, IDENTITY.md — immutable core
- T1 (Long-term): MEMORY.md — curated, promoted from T2
- T2 (Short-term): memory/*.md — daily logs, topic files
- T3 (Session): Current conversation context
Operations
- Search: Grep across all memory files for relevant context
- Sync: Git add/commit/push memory files to remote
- Compact: Summarize old entries, promote to MEMORY.md
- Resolve: Handle merge conflicts in memory files (prefer newer + human edits)
Best practices
- Topic files:
memory/topic-*.md(max 30 lines history, 50 lines decisions) - Daily logs:
memory/YYYY-MM-DD.md - Always commit memory changes with descriptive messages
- Search memory before answering questions about prior work
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.