remember
Skill1 starsChanged 4 days agoMITView on GitHub
Save something to the brain right now. Use it when the user says "remember this", "note this down", "don't forget", "keep it for next time", or asks to see or correct what is already remembered.
70 other projects use a version of this.
Adopted by
Most recently taken up by
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- priyansh1210/shirotheir own version, first seen Nov 8, 2026
- jsmastery-pro/jsm-hqtheir own version, first seen Nov 8, 2026
- ArcticFox2029/chamnantheir own version, first seen Nov 5, 2026
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
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.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- parcadeiSkill
agentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions70 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 70
- github/awesome-copilot★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- langchain-ai/deepagents★ 31ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- H-mmer/pentest-agents★ 815same name
- SparkDevNetwork/Rock★ 701same name
60 more not listed
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 repository3 other files it gives its agents.
- docs/agents.mdAGENTS.md
- close-sessionSkill
- memory-keepingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 62 edited versions we read keep these.
0
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
- Very specific: line 18
Before creating a note, grep memory/ in case one exists that should be updated.
- Very specific: line 20
Write the note with complete frontmatter (verified set to today, status: current), add the line to the index of its area …
- Very specific: line 23
Run bin/health.py to make sure the index is not out of step and no link is broken.
“Common” is measured: kept by at least 6 in 10 of the 62 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
Remember
The user wants something to survive this conversation. Do it before moving on: if the session is cut, it is lost.
If asked to save something
- Decide where it goes, using the rules of the
memory-keepingskill:- a fact, a decision or a preference: a note in
memory/ - a repeatable procedure: a new skill in
skills/ - something half done or waiting for their decision: a line in
PENDING.md - something the machine already knows (addresses, RAM, ports): do not save it, it is in
inventory/
- a fact, a decision or a preference: a note in
- Before creating a note,
grepmemory/in case one exists that should be updated. Two notes that contradict each other are worse than one outdated note. - Write the note with complete frontmatter (
verifiedset to today,status: current), add the line to the index of its area (memory/index-*.md, neverMEMORY.md), and link it from related notes with[[name]]. - Run
bin/health.pyto make sure the index is not out of step and no link is broken. - Confirm in one line what was saved and where. Do not show the whole file.
If asked what is remembered
grep -i "<topic>" memory/index-*.md
grep -ril "<topic>" memory/Summarise what you find in your own words; do not dump raw markdown.
If told that something remembered is wrong
Fix it at once. Edit the existing note (do not create a second one), move the old content to a
## Before section if it deserves keeping, and set verified to today. Having been corrected is
the strongest sign that this had to be stored properly.
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.