remember

Save current work session summaries and file metadata to persistent memory.

6|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/mahmoudimus/simba --skill remember-mahmoudimus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/mahmoudimus/simba/tree/main/skills/remember
Command: npx skills add https://github.com/mahmoudimus/simba --skill remember-mahmoudimus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires simba.search, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of saving your current work session's context, accomplishments, and learnings into a persistent memory, ensuring continuity and providing valuable context for future interactions.

Core Features & Use Cases

  • Session Summarization: Automatically generates a concise summary of your work.
  • Activity Tracking: Records files modified, decisions made, and key learnings.
  • Knowledge Management: Allows for saving specific code area knowledge and project facts.
  • Use Case: After a long coding session where you refactored a complex module, you can use /remember to save a summary of the changes, the files affected, and any new insights about the module's architecture, making it easy to pick up where you left off later.

Quick Start

Use the remember skill to save the current work session to persistent memory.

Frequently Asked Questions about remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save my coding session context for future continuity?

To save coding session context for future continuity, you can use a summarization tool that analyzes activity logs, generates concise summaries of accomplishments, and tracks modified files. This stores your work session into persistent memory, ensuring cross-session context retrieval.

What is persistent memory for cross-session work continuity?

Persistent memory for cross-session continuity is a storage mechanism that retains summaries of modified files, project facts, and key learnings. It allows future interactions to access previous activity logs and metadata without losing context between separate work periods.

How do I track modified files and extract metadata from a work session?

To track modified files and extract metadata from a work session, the tool analyzes activity logs to identify touched files and relevant topics. It then extracts this metadata and saves it alongside a generated summary to persistent memory.

Can I save project facts and code area knowledge alongside session summaries?

Yes, you can save project facts and code area knowledge alongside session summaries. The tool optionally allows you to add specific architectural insights and project facts before storing the complete context and clearing the activity log.

Does saving session memory require simba.search?

Yes, saving session memory requires the simba.search dependency. The tool utilizes the simba.search CLI to store the extracted metadata, project facts, and generated summaries into the persistent memory backend.