How do I install the Memory Save skill?

Run npx skillmds add majiayu000/memory-save 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 Memory Save safe to use?

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

Which AI agents work with Memory Save?

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 Memory Save free to use?

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

Who published Memory Save?

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

Memory Save by majiayu000 — Agent Skill

Name: Memory Save
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Script Path Resolution

IMPORTANT: The scripts/ folder is in the plugin directory, NOT the current project.

From "Base directory for this skill:" above, derive the scripts path:

Remove /skills/memory-save from the end
Add /scripts/ to get the scripts directory

Example:

Base: ~/.claude/plugins/cache/memory-keeper-marketplace/memory-keeper/13.8.3/skills/memory-save
Scripts: ~/.claude/plugins/cache/memory-keeper-marketplace/memory-keeper/13.8.3/scripts/

Use this full path when running node commands below.

Memory Save Skill (v13.1.0)

This skill activates when [MEMORY_KEEPER] appears in conversation.

Memory Structure

.claude/memory/
  project.md        <- Project overview (stable)
  architecture.md   <- Architecture decisions (stable)
  conventions.md    <- Coding conventions (stable)
  memory.md         <- Rolling session log (last 50 lines loaded)
  sessions/         <- L1 session transcripts (auto-generated)
  logs/             <- Debug and error logs

Trigger Message

═══════════════════════════════════════════════════════════════
[MEMORY_KEEPER] AUTO-SAVE TRIGGERED - N tool uses reached
═══════════════════════════════════════════════════════════════

Required Actions

Step 1: Save to memory.md

printf '\n## %s\n%s\n' "$(date +%Y-%m-%d_%H%M)" "[1-2 sentence summary]" >> ".claude/memory/memory.md"

Session End (Stop Hook)

Additional step (use full path from above):

node "{SCRIPTS_PATH}/counter.js" compress

Optional: Update Hierarchical Memory

If major project understanding changed, update stable memory files (use full path):

node "{SCRIPTS_PATH}/counter.js" memory-set project "Updated project description..."
node "{SCRIPTS_PATH}/counter.js" memory-set architecture "Updated architecture..."
node "{SCRIPTS_PATH}/counter.js" memory-set conventions "Updated conventions..."

When to update:

project.md: New project scope, goals, or tech stack
architecture.md: New architecture decisions or patterns
conventions.md: New coding standards or workflows

View current memory:

node "{SCRIPTS_PATH}/counter.js" memory-list
node "{SCRIPTS_PATH}/counter.js" memory-get project

Critical

DO NOT SKIP the memory.md append step
Counter resets automatically (no manual reset needed)

See Architecture for full details.

---name: memory-savedescription: Execute when you see "[MEMORY_KEEPER]" in hook output. Follow the numbered steps exactly to save session memory.--- ## Script Path Resolution **IMPORTANT:** The `scripts/` folder is in the plugin directory, NOT the current project. From "Base directory for this skill:" above, derive the scripts path: - Remove `/skills/memory-save` from the end - Add `/scripts/` to get the scripts directory Example: - Base: `~/.claude/plugins/cache/memory-keeper-marketplace/memory-keeper/13.8.3/skills/memory-save` - Scripts: `~/.claude/plugins/cache/memory-keeper-marketplace/memory-keeper/13.8.3/scripts/` Use this full path when running node commands below. # Memory Save Skill (v13.1.0) This skill activates when `[MEMORY_KEEPER]` appears in conversation. ## Memory Structure ``` .claude/memory/ project.md <- Project overview (stable) architecture.md <- Architecture decisions (stable) conventions.md <- Coding conventions (stable) memory.md <- Rolling session log (last 50 lines loaded) sessions/ <- L1 session transcripts (auto-generated) logs/ <- Debug and error logs ``` ## Trigger Message ``` ═══════════════════════════════════════════════════════════════ [MEMORY_KEEPER] AUTO-SAVE TRIGGERED - N tool uses reached ═══════════════════════════════════════════════════════════════ ``` ## Required Actions ### Step 1: Save to memory.md ```bash printf '\n## %s\n%s\n' "$(date +%Y-%m-%d_%H%M)" "[1-2 sentence summary]" >> ".claude/memory/memory.md" ``` ## Session End (Stop Hook) Additional step (use full path from above): ```bash node "{SCRIPTS_PATH}/counter.js" compress ``` ## Optional: Update Hierarchical Memory If major project understanding changed, update stable memory files (use full path): ```bash node "{SCRIPTS_PATH}/counter.js" memory-set project "Updated project description..." node "{SCRIPTS_PATH}/counter.js" memory-set architecture "Updated architecture..." node "{SCRIPTS_PATH}/counter.js" memory-set conventions "Updated conventions..." ``` **When to update:** - `project.md`: New project scope, goals, or tech stack - `architecture.md`: New architecture decisions or patterns - `conventions.md`: New coding standards or workflows **View current memory:** ```bash node "{SCRIPTS_PATH}/counter.js" memory-list node "{SCRIPTS_PATH}/counter.js" memory-get project ``` ## Critical - **DO NOT SKIP** the memory.md append step - Counter resets automatically (no manual reset needed) See [Architecture](../../docs/ARCHITECTURE.md) for full details.

Frequently asked questions