update-memory

Upsert key-value entries into an existing memory.md file.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/adamrdrew/claude-code-patterns --skill update-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-memory
Source: https://github.com/adamrdrew/claude-code-patterns/tree/main/skill-discovery/.claude/skills/update-memory
Command: npx skills add https://github.com/adamrdrew/claude-code-patterns --skill update-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upsert memory entries by key into the memory persistence system, enabling seamless updates and additions without manual editing.

Core Features & Use Cases

  • Upserts: update existing keys or add new ones in memory.md.
  • Safe precondition: requires memory.md to exist; if not, the process halts with guidance.
  • Use cases: store user preferences, session state, and lightweight configuration data across interactions.

Quick Start

Set a memory entry by providing a key and value to upsert, e.g., add - user_id: 12345 to memory.md.

Frequently Asked Questions about update-memory

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

FAQPage Schema
How do I upsert key-value memory entries in memory.md for Claude Code?

You can upsert memory entries by providing a key and value to update or append data in memory.md. This updates existing keys or adds new ones without manual editing.

What happens if I try to update memory.md before the file exists?

The upsert process halts if memory.md does not exist. It enforces this safe precondition and provides guidance rather than creating the file automatically.

How does subagent memory persistence work for storing user preferences?

Subagent memory persistence stores lightweight key-value data like user preferences or session state across interactions by upserting entries into memory.md.

Can I use this to store session state across multiple Claude Code interactions?

Yes, you can store session state across interactions by upserting key-value pairs into memory.md. This allows lightweight configuration data to persist seamlessly.

What is the best way to modify existing keys in a memory persistence system?

The best way to modify existing keys is an upsert operation, which checks memory.md for the key and updates it in place, or appends it if the key is new.

Why does my memory upsert halt with a missing file error?

Your memory upsert halts because it requires memory.md to exist as a precondition. You must create the file first before storing or modifying key-value data.