search-memory
Skill17 starsChanged 7 months agoMITView on GitHub
Search through all past daily logs, cold memory files, and conversation history. Use when {{OWNER_NAME}} asks "when did we...", "do you remember...", "what did I say about...", or needs context from a past session.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- YehudaFrankel/clankbraintheir own version, first seen Apr 16, 2026
- couzip/cc-forevertheir own version, first seen Feb 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- YehudaFrankel/clankbrain★ 16same name
- couzip/cc-forever★ 2same 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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-standupSkill
- distill-sessionSkill
- heartbeatSkill
- humanizerSkill
- memory-updateSkill
- playwright-cliSkill
- promoteSkill
- researchSkill
- self-improveSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 7
Search the memory system for past context:
- Distinctive: line 17
Ensure the index is up to date:
- Distinctive: line 22
Search using FTS5 syntax:
- Distinctive: line 36
If the search returns results, read the full source file for more context if needed.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Search the memory system for past context:
Search Order
- Check hot memory first — read
identity/memory.md(already in context, might have the answer) - Check cold memory — read relevant
memory/*.mdfiles (projects, decisions, preferences, people) - Search daily log archive — FTS5 full-text search for raw conversation history
Daily Log Search
- Ensure the index is up to date:
python3 .claude/scripts/index-daily-logs.py Search using FTS5 syntax:
python3 .claude/scripts/search-logs.py "$ARGUMENTS"Supported query syntax:
- Simple words:
typescript testing - Phrases:
"pull request" - Boolean:
deploy AND production - Negation:
api NOT graphql - Prefix:
auth* - Date filter:
--date 2026-04-05 - Limit:
--limit 20
- Simple words:
- If the search returns results, read the full source file for more context if needed.
- Synthesize findings into a clear answer. Don't dump raw results — summarize what's relevant to the question.
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.

