memory

Store durable project facts with subjects, predicates, quotes, and scope hints.

23|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/codenamev/claude_memory --skill memory-codenamev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/codenamev/claude_memory/tree/main/skills/memory
Command: npx skills add https://github.com/codenamev/claude_memory --skill memory-codenamev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores and recalls important facts across conversations, enabling durable knowledge persistence across sessions for projects and preferences.

Core Features & Use Cases

  • Durable, long-term memory for project-specific and global information.
  • Tools to store facts with quotes and provenance (memory.store_extraction) and to recall (memory.recall) or explain (memory.explain).
  • Use cases include capturing tech stacks, conventions, decisions, and user preferences to accelerate future work.

Quick Start

After a productive conversation, store key facts with memory.store_extraction to persist them for future sessions.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I persist project knowledge across sessions so I don't lose context?▼

To persist project knowledge across sessions, you can store durable facts like tech stack details and conventions using memory.store_extraction, ensuring important information survives beyond a single conversation.

What is the best way to store structured facts like tech stack decisions for later recall?▼

The best way to store structured facts is by providing subjects, predicates, quotes, and scope hints to a persistence tool, which captures decisions and preferences for reliable long-term recall.

How do I recall previously stored project facts and trace their provenance?▼

You can recall previously stored project facts using memory.recall, and trace the exact origin and context of those facts using the memory.explain tool to verify their provenance.

Can I use long-term memory to save both global preferences and project-specific conventions?▼

Yes, you can save both global preferences and project-specific conventions. The persistence tools support scope hints, allowing you to separate user-wide preferences from localized project knowledge.

What format do I need to provide facts in to ensure they are stored correctly?▼

You need to provide facts as structured data containing subjects, predicates, quotes, and scope hints. This structured format is required to successfully persist knowledge using memory.store_extraction.