How do I install the Session Memory skill?

Run npx skillmds@latest add rhythmmittal19/session-memory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Session Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Session Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Session Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Session Memory?

RhythmMittal19 (@rhythmmittal19) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Session Memory by rhythmmittal19 — Agent Skill

Name: Session Memory
Author: RhythmMittal19

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.

File contents

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.md in the project root
Look for .claude/session-handoff.md from 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.md with 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]

Frequently asked questions