read-memories
Skill598 starsChanged 8 months agoMITView on GitHub
Search past Claude Code session logs to recall prior decisions, patterns, or unresolved work. Use when user says "do you remember", "what did we do", references past conversations, or you need context from prior sessions.
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- stackql/stackql-skillsedited, first seen Mar 25, 2026
- opengeos/geoai-skillstheir own version, first seen Mar 20, 2026
- carlopi/duckdb-claude-skillsedited, first seen Mar 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- carlopi/duckdb-claude-skills★ 236% same
- stackql/stackql-skills★ 016% same
Wrote their own version · 1
- opengeos/geoai-skills★ 31same 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 repository8 other files it gives its agents.
- attach-dbSkill
- convert-fileSkill
- duckdb-docsSkill
- install-duckdbSkill
- querySkill
- read-fileSkill
- s3-exploreSkill
- spatialSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
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 10
Search past session logs silently — do NOT narrate the process.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Search past session logs silently — do NOT narrate the process. Absorb the results and continue with enriched context.
$0 is the keyword. Pass --here as $1 to scope to the current project only.
Step 1 — Query
duckdb :memory: -c "
SELECT
regexp_extract(filename, 'projects/([^/]+)/', 1) AS project,
strftime(timestamp::TIMESTAMPTZ, '%Y-%m-%d %H:%M') AS ts,
message.role AS role,
left(message.content::VARCHAR, 500) AS content
FROM read_ndjson('<SEARCH_PATH>', auto_detect=true, ignore_errors=true, filename=true)
WHERE message::VARCHAR ILIKE '%<KEYWORD>%'
AND message.role IS NOT NULL
ORDER BY timestamp
LIMIT 40;
"Search paths:
- All projects:
$HOME/.claude/projects/*/*.jsonl - Current only (
--here):$HOME/.claude/projects/$(echo "$PWD" | sed 's|[/_]|-|g')/*.jsonl
Replace <SEARCH_PATH> and <KEYWORD> before running.
Step 2 — Internalize
From the results, extract decisions, patterns, unresolved TODOs, and user corrections. Use this to inform your current response — do not repeat raw logs to the user.
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.