Claude-skill-registry-data memory-save

Execute when you see "[MEMORY_KEEPER]" in hook output. Follow the numbered steps exactly to save session memory.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry-data
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/memory-save" ~/.claude/skills/majiayu000-claude-skill-registry-data-memory-save && rm -rf "$T"
manifest: data/memory-save/SKILL.md
source content

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.