session-memory
Skill0 starsChanged 8 months agoMITView on GitHub
Bridges Code tab sessions with the Memory MCP server. Use at session start to load relevant project memories, and at session end to store new discoveries. Activates when working on any project to maintain continuity across sessions.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- GeekFamilyCorp/TricorderKittheir own version, first seen Nov 8, 2026
- apappascs/claude-code-sessionstheir own version, first seen Nov 1, 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
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
- apappascs/claude-code-sessions★ 2same name
- InanisV/my-claude-skills★ 1same name
- Caelumca/claude-codex-skeleton★ 0same name
- ieteerapat/ClaudeSkills1.0★ 0same name
- KogaCyber/jarvis-skills★ 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 repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commitSkill
- consolidate-learningsSkill
- dailySkill
- debugSkill
- handoffSkill
- init-projectSkill
- learnings-loopSkill
- optimizeSkill
- planSkill
- project-detectorSkill
- quick-researchSkill
- reflectSkill
- reviewSkill
- scaffoldSkill
- strategic-compactSkill
- teachSkill
- testSkill
- wrapSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Check if the memory MCP server has entries for this project:
- Very specific: line 17
Look for learnings.md in the project root
- Very specific: line 18
Look for .claude/session-handoff.md from previous sessions
- Very specific: line 31
Update learnings.md with new discoveries
- Very specific: line 32
If ending a long session, create .claude/session-handoff.md
“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
Session Memory Bridge
Purpose
The Memory MCP server persists facts across Claude Desktop conversations. This skill helps Claude Code sessions (Code tab) leverage that same memory.
At Session Start
- Check if the memory MCP server has entries for this project:
echo "Project: $(basename $(pwd))" - Look for
learnings.mdin the project root - Look for
.claude/session-handoff.mdfrom previous sessions - Apply all relevant context before starting work
During Work — What to Remember
Store these types of facts (for the Memory MCP in Desktop chat later):
- Architecture decisions: "Project X uses JWT auth with refresh tokens in httpOnly cookies"
- Conventions discovered: "In project X, all API calls go through services/ layer"
- Gotchas found: "In project X, the test DB must be seeded before running integration tests"
- Dependencies: "Project X requires Node 20+ and MongoDB 7+"
- Current state: "Project X has auth module complete, payment module in progress"
At Session End
- Generate a summary of what was done
- Update
learnings.mdwith new discoveries - If ending a long session, create
.claude/session-handoff.md - Suggest facts to store in Memory MCP (user can do this in Desktop chat)
Session Handoff Format
## Session Handoff — [date]
### Done: [list of completed work]
### Decisions: [architecture/design choices made]
### State: [what's working, what's in progress]
### Issues: [bugs found, blockers, tech debt]
### Next: [prioritized next steps]
### Files: [key files modified]
### Memory Suggestions: [facts to tell Memory MCP in Desktop chat]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.