agent-memory

Store persistent memories with YAML frontmatter across conversations.

Updated Sep 4, 2022
One-click install
npx skills add https://github.com/yt3trees/dotfiles --skill agent-memory-yt3trees
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-memory
Source: https://github.com/yt3trees/dotfiles/tree/main/.claude/skills/agent-memory
Command: npx skills add https://github.com/yt3trees/dotfiles --skill agent-memory-yt3trees

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a persistent memory space for storing knowledge that survives across conversations, solving the problem of ephemeral context and lost decisions.

Core Features & Use Cases

  • Persistent memory store at .claude/skills/agent-memory/memories/ to keep notes and decisions.
  • Proactive usage guidance to save, review, and reorganize memories as context evolves.
  • Simple, category-based organization and search-friendly summaries for efficient recall.

Quick Start

To save a memory, create a new file under a category, e.g. .claude/skills/agent-memory/memories/project-context/december-2025-work.md, with frontmatter:

summary: "December 2025 project context and decisions" created: 2025-12-01

Then add your content below to capture goals, decisions, and next steps.

Frequently Asked Questions about agent-memory

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

FAQPage Schema
How do I persist context and decisions across conversations?

The memory mechanism works by saving notes into a persistent folder structure with YAML frontmatter summaries, letting you retrieve and organize past context during ongoing tasks without losing decisions.

How do I save and recall memories during research and planning tasks?

You save memories by creating categorized Markdown files with YAML frontmatter, then recall them through a simple retrieval workflow that searches the summary fields to find relevant past context.

Do I need any dependencies or external tools to organize persistent notes?

No external dependencies are required to store and recall persistent memories; the system operates independently using standard Markdown files and YAML frontmatter within a dedicated local folder.

What's the best way to organize persistent memories for efficient recall?

The best way to organize memories is using category-based folders with search-friendly YAML frontmatter summaries, enabling efficient recall and proactive reorganization as your context evolves.

When should I not use a file-based memory approach for context persistence?

A file-based memory approach is not ideal for highly relational data or automated real-time retrieval, since it relies on simple category-based folders and manual search-friendly summaries.