Remember Session

VerifiedSafe

Summarizes and saves the current work session to persistent memory, tracking accomplishments, files modified, and key learnings for cross-session continuity. Use this to preserve context and recall past work in future sessions.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#session-memory#context-save#workflow-continuity#activity-log

Recommended for

Automated summary

Saves the current work session to persistent memory for future context, summarizing accomplishments and tracking modified files.

Strengths

  • Enables cross-session continuity by preserving context
  • Automatically extracts key metadata and topics
  • Optionally stores knowledge and facts about the codebase

Limitations

  • Requires external tool (simba.search) to be installed and configured
  • Summary quality depends on automatic activity log analysis
  • Memory is not shared across different projects
When to use it

When finishing a significant work session and you want to resume later without losing context.

When not to use it

If the project lacks the persistent memory tool or the session produced no meaningful changes.

Security analysis

Safe
Quality score92/100

The skill executes only safe Bash commands for reading activity logs, running a Python CLI tool, and deleting a specific log file. There are no destructive, exfiltrating, or obfuscated operations.

No concerns found

How this analysis is made

Examples

Save session with default summary
/remember
Save session and add a fact
Remember that this project uses PostgreSQL with Prisma ORM and then run /remember
Save session with knowledge about auth module
Remember how the auth module works and then save the session with /remember

name: remember description: Save the current work session to persistent memory for future context. Summarizes accomplishments, tracks files modified, and stores learnings for cross-session continuity.

/remember - Save Session to Memory

Summarize the current work session and save it to persistent memory for future context.

Instructions

When the user invokes /remember, you should:

1. Check for Activity Log

First, check if there's an activity log from this session:

REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "$PWD")
ACTIVITY_FILE="$REPO_ROOT/.simba/search/activity.log"
if [ -f "$ACTIVITY_FILE" ]; then
    cat "$ACTIVITY_FILE"
fi

2. Analyze the Session

Review what was accomplished in this conversation:

  • What files were read, created, or modified?
  • What was the main goal or task?
  • What key decisions were made?
  • Were there any important patterns or learnings?

3. Generate Summary

Create a concise summary (2-3 sentences) that captures:

  • What was done (the main accomplishment)
  • Why it matters (the purpose or problem solved)
  • Key details (important files, patterns, or decisions)

4. Extract Metadata

Identify:

  • Files touched: List of file paths worked on
  • Topics: 3-5 keywords for searchability (e.g., "auth, jwt, middleware, security")
  • Tools used: Main tools used (Read, Write, Edit, Bash, etc.)

5. Save to Memory

Use the simba.search CLI to save:

# Initialize if needed
uv run python -m simba.search init

# Save session
uv run python -m simba.search add-session \
    "YOUR_SUMMARY_HERE" \
    '["file1.ts", "file2.ts"]' \
    '["Read", "Edit", "Bash"]' \
    "topic1, topic2, topic3"

6. Optionally Add Knowledge or Facts

If during the session you learned something important about the codebase that should be remembered:

For code area knowledge:

uv run python -m simba.search add-knowledge \
    "src/auth" \
    "Authentication module using JWT tokens with refresh token rotation" \
    "Tokens expire in 15min, refresh tokens in 7 days"

For project facts:

uv run python -m simba.search add-fact \
    "Uses PostgreSQL with Prisma ORM" "architecture"
uv run python -m simba.search add-fact \
    "All API routes require authentication except /health" "convention"

7. Clear Activity Log

After saving, clear the activity log:

REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "$PWD")
ACTIVITY_FILE="$REPO_ROOT/.simba/search/activity.log"
[ -f "$ACTIVITY_FILE" ] && rm "$ACTIVITY_FILE"

8. Confirm to User

Report what was saved:

Saved to memory:
- Summary: [your summary]
- Topics: [topics]
- Files: [count] files tracked

Memory now contains [X] sessions. Use /memory-stats to see details.

Example Output

Saved to memory:
- Summary: Implemented JWT authentication with refresh token rotation. Added middleware for protected routes and updated user model with token fields.
- Topics: auth, jwt, middleware, tokens, security
- Files: 4 files tracked

Memory now contains 12 sessions.

Additional Commands

If the user wants to add specific knowledge or facts, they can say:

  • "Remember that this project uses X" -> Add as fact
  • "Remember how the auth module works" -> Add as knowledge

Ask clarifying questions if the summary scope is unclear.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/remember-session-mmk3ni67/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/remember-session-mmk3ni67' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/remember-session-mmk3ni67/download' --output '.skill-downloads/remember-session-mmk3ni67/SKILL.md.part' && mv '.skill-downloads/remember-session-mmk3ni67/SKILL.md.part' '.skill-downloads/remember-session-mmk3ni67/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/remember-session-mmk3ni67/SKILL.md' && test -s '.skill-downloads/remember-session-mmk3ni67/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/remember' && cp -R '.skill-downloads/remember-session-mmk3ni67' '.claude/skills/remember'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/remember-session-mmk3ni67'

openskills read 'remember-session-mmk3ni67'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/remember-session-mmk3ni67/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills