session-memory
Skill2 starsChanged 26 days agoMITView on GitHub
Searches and lists all Claude Code memories across projects. Use when the user asks what memories exist, wants to see stored knowledge, asks "what do you remember", or wants an overview of their memory files. Also triggered by: "list memories", "show memories", "what's in my memory".
12 other projects use a version of this.
Adopted by
Most recently taken up by
- GeekFamilyCorp/TricorderKittheir own version, first seen Nov 8, 2026
- alexeyban/EKOStheir own version, first seen Nov 1, 2026
- InanisV/my-claude-skillstheir own version, first seen Aug 22, 2026
- Caelumca/claude-codex-skeletontheir own version, first seen Aug 18, 2026
- KogaCyber/jarvis-skillstheir own version, first seen Aug 17, 2026
- moriwo-dev-ai/amateras-registrytheir own version, first seen Jul 26, 2026
Used with
Projects with it also use skill-creator.
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.
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 4 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- oaustegard/claude-skills★ 158same name
- GeekFamilyCorp/TricorderKit★ 32same name
- alexeyban/EKOS★ 26same name
- DangQuangSE/team-development-skills★ 19same name
- lukasreese/claude-skills-starter-kit★ 3same name
- InanisV/my-claude-skills★ 1same name
- Caelumca/claude-codex-skeleton★ 0same name
- ieteerapat/ClaudeSkills1.0★ 0same name
- KogaCyber/jarvis-skills★ 0same name
- Mesteriis/Engineering-Bible-AI★ 0same name
2 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 repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- session-cleanupSkill
- session-deleteSkill
- session-detailSkill
- session-diffSkill
- session-exportSkill
- session-listSkill
- session-memory-auditSkill
- session-memory-searchSkill
- session-resumeSkill
- session-searchSkill
- session-statsSkill
- session-tasksSkill
- session-timelineSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run the memory scanner to discover all memory files across projects:
- Very specific: line 36
If any memory has indexed: false, note it: "N memories not indexed in MEMORY.md — run /session-memory-audit to fix"
- Very specific: line 37
If any memory has has_frontmatter: false, note it: "N memories missing frontmatter"
“Common” is measured: kept by at least 6 in 10 of the 11 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
Step 1: Scan all memories
Run the memory scanner to discover all memory files across projects:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/memory-scanner.ts scanOptional filters — add based on user request:
--type user|feedback|project|reference— filter by memory type--project FILTER— filter by project name (substring match)
Step 2: Present the results
Parse the JSON output and present as a grouped-by-project table:
For each project that has memories, show:
| # | Name | Type | Age | Indexed |
| 1 | Memory name | type | Nd | yes/no |
At the top, show the summary line:
Found N memories across M projects — N user, N feedback, N project, N reference
Highlight issues if visible:
- If any memory has
indexed: false, note it: "N memories not indexed in MEMORY.md — run/session-memory-auditto fix" - If any memory has
has_frontmatter: false, note it: "N memories missing frontmatter"
Step 3: Suggest follow-ups
Based on what was found, suggest relevant next steps:
- "/session-memory-audit" — to health-check and fix issues
- "/session-memory-search
<keyword>" — to search across memory content
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.