Memory Protocol

This enforces a strict discipline around using Memento MCP as your cross-session knowledge graph. The core idea: always search memory before starting work or debugging, use two-dimensional queries (technical topic plus process learnings), and always traverse the full graph with open_nodes and relations, not just the search summaries. It's opinionated about preventing the split-brain problem where you store things in both files and Memento. The value is compounding feedback loops where yesterday's lessons actually inform today's work instead of getting lost between sessions. If you're not already using Memento MCP, this won't help you, it just fails gracefully and tells you to install it.

skills.sh installs: 248
GitHub stars: 5
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwilger/agent-skills --skill memory-protocol --agent claude-code

Installs into .claude/skills of the current project.

Files

Memory Protocol

Value: Feedback -- accumulated knowledge creates compound feedback loops across sessions. What you learn today should accelerate tomorrow's work.

Purpose

Teaches the agent to systematically store and recall project knowledge across sessions using the Memento MCP knowledge graph.

Your long-term memory (training data) and short-term memory (context window) are excellent, but mid-term memory for project-specific knowledge outside the current context is poor. Memento addresses this gap by persisting a knowledge graph across sessions and projects.

Solves: context loss between sessions, repeated debugging of known issues, rediscovery of established conventions, repeated user corrections for the same mistakes.