memory-extractor
Skill236 starsChanged 8 months agoMITView on GitHub
Extract durable memories from recent conversation turns into user, feedback, project, and reference categories while avoiding stale code-state facts.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- HanksChen0110/skillsword for word, first seen Oct 3, 2026
Other versions1 project uses a version of this.
Word for word · 1
- HanksChen0110/skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository5 other files it gives its agents.
- dream-memorySkill
- kairos-liteSkill
- structured-context-compressorSkill
- swarm-coordinatorSkill
- verification-gateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 8
Use this skill when you want to persist durable collaboration context from the latest conversation turns.
- Distinctive: line 43
avoid code-state facts that can drift
- Distinctive: line 44
prefer updating an existing topic file
≈ “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
Memory Extractor
Use this skill when you want to persist durable collaboration context from the latest conversation turns.
Use It For
- capturing user preferences
- saving feedback about how to work
- recording non-code project constraints or deadlines
- storing pointers to external systems
Avoid It For
- storing code structure or file locations
- saving short-lived task state that belongs in a plan
- duplicating an existing memory topic without checking first
Quick Start
Build a manifest of existing memories:
python3 {baseDir}/scripts/memory_manifest.py --memory-root /path/to/memoryThen use the portable prompt in references/prompt-template.md.
Four Types
userfeedbackprojectreference
Rules
- save only durable signals
- avoid code-state facts that can drift
- prefer updating an existing topic file
- organize by topic, not chronology
Supporting Files
- Prompt template: references/prompt-template.md
- Source notes: references/source-notes.md
- Helper script:
python3 {baseDir}/scripts/memory_manifest.py ...
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.