save-memory

Persist session context to daily memory files and MEMORY.md.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/dcarmitage/claws --skill save-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-memory
Source: https://github.com/dcarmitage/claws/tree/main/skills/save-memory
Command: npx skills add https://github.com/dcarmitage/claws --skill save-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill saves end-of-session memory by persisting full context to both daily memory files and MEMORY.md, enabling seamless handoffs between sessions.

Core Features & Use Cases

  • End-of-session memory capture: records what changed, why, and how it connects to ongoing work to avoid context loss.
  • Daily memory & MEMORY.md updates: writes structured notes so the next session can resume quickly.
  • Detected triggers and workflow: ensures memory is saved before session termination or major changes.

Quick Start

Use the save-memory skill to capture the current session state and update MEMORY.md and the daily memory file for today.

Frequently Asked Questions about save-memory

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

FAQPage Schema
How do I preserve session context across multiple bash automation runs?

To preserve session context across bash automation runs, you can persist full session state to daily memory files and MEMORY.md. This captures changes, builds, and decisions so the next session resumes without context loss.

What is the best way to save end-of-session memory for seamless handoffs?

The best way to save end-of-session memory for seamless handoffs is writing structured notes to both daily memory files and MEMORY.md. This records what changed and why, enabling the next session to resume quickly.

Do I need external dependencies to persist memory to MEMORY.md using shell commands?

No, you do not need external dependencies to persist memory to MEMORY.md. This memory management approach uses standard shell commands to gather context and update designated memory files without requiring any external installations.

When should I update daily memory files during a development workflow?

You should update daily memory files during session wrap-up, before session termination, or before major changes. This ensures all current context is captured for memory management and seamless handoffs to the next run.

Can I use standard shell commands to capture build decisions and changes for memory management?

Yes, you can use standard shell commands to capture build decisions and changes for memory management. The process gathers context and updates MEMORY.md and daily memory files without needing any external installations or frameworks.