Session memory
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.From its SKILL.md
npx -y skills add RhythmMittal19/claude-config --skill session-memoryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 387 tokens by cl100k_base, as published. Nobody here has run it
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]
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.