How do I install the Memory skill?

Run npx skillmds@latest add tomevault-io/memory-6 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Memory?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memory by tomevault-io — Agent Skill

Name: Memory
Author: tomevault-io

File contents

Claude Cortex — Memory System

You have access to a persistent memory system via MCP tools (remember, recall, get_context, forget).

MUST use remember immediately when any of these occur:

A decision is made (architecture, library choice, approach)
A bug is fixed (capture root cause + solution)
Something new is learned about the codebase
User states a preference
A significant feature is completed

Do not wait until the end of the session. Call remember right after the event happens.

Tools

Tool	Purpose
`remember`	Store a memory with title, content, category, importance
`recall`	Search memories by query, category, tags
`get_context`	Load relevant project context (architecture, patterns, preferences)
`forget`	Delete memories by ID or query
`start_session`	Begin a session and load context
`end_session`	End session and trigger consolidation
`memory_stats`	View memory statistics
`graph_query`	Traverse the knowledge graph
`graph_entities`	List entities in the knowledge graph
`detect_contradictions`	Find conflicting memories

When to Use `remember`

After making a decision: "Decided to use PostgreSQL for better JSON support"
After fixing a bug: "Auth bug caused by expired JWT tokens"
After learning something: "SQLite FTS5 requires escaping hyphens"
For architecture choices: "Using microservices pattern with API gateway"
For user preferences: "User prefers TypeScript strict mode"

Best Practices

Call remember immediately when something important happens
Include context: what, why, and any relevant code/file references
Use clear titles that summarize the key point
Tag with relevant categories (architecture, error, learning, preference)

What Gets Auto-Extracted by Hooks

The PreCompact and SessionEnd hooks automatically extract high-salience content:

Decisions: "decided to...", "going with...", "chose...", "using..."
Error fixes: "fixed by...", "the solution was...", "root cause..."
Learnings: "learned that...", "discovered...", "turns out..."
Architecture: "created...", "implemented...", "refactored..."
Preferences: "always...", "never...", "prefer to..."
Notes: "important:", "remember:", "key point..."

Don't rely solely on auto-extraction. Use remember proactively for important events.

Source: mkdelta221/claude-cortex — distributed by TomeVault.

---name: memory-6description: Persistent memory system — use proactively to remember decisions, fixes, learnings, and preferences across sessions. Invoke when you need to save or recall important context. Use when this capability is needed.---# Claude Cortex — Memory SystemYou have access to a persistent memory system via MCP tools (`remember`, `recall`, `get_context`, `forget`).**MUST use `remember` immediately when any of these occur:**- A decision is made (architecture, library choice, approach)- A bug is fixed (capture root cause + solution)- Something new is learned about the codebase- User states a preference- A significant feature is completedDo not wait until the end of the session. Call `remember` right after the event happens.## Tools| Tool | Purpose ||------|---------|| `remember` | Store a memory with title, content, category, importance || `recall` | Search memories by query, category, tags || `get_context` | Load relevant project context (architecture, patterns, preferences) || `forget` | Delete memories by ID or query || `start_session` | Begin a session and load context || `end_session` | End session and trigger consolidation || `memory_stats` | View memory statistics || `graph_query` | Traverse the knowledge graph || `graph_entities` | List entities in the knowledge graph || `detect_contradictions` | Find conflicting memories |## When to Use `remember`- **After making a decision**: "Decided to use PostgreSQL for better JSON support"- **After fixing a bug**: "Auth bug caused by expired JWT tokens"- **After learning something**: "SQLite FTS5 requires escaping hyphens"- **For architecture choices**: "Using microservices pattern with API gateway"- **For user preferences**: "User prefers TypeScript strict mode"## Best Practices1. Call `remember` immediately when something important happens2. Include context: what, why, and any relevant code/file references3. Use clear titles that summarize the key point4. Tag with relevant categories (architecture, error, learning, preference)## What Gets Auto-Extracted by HooksThe PreCompact and SessionEnd hooks automatically extract high-salience content:- **Decisions**: "decided to...", "going with...", "chose...", "using..."- **Error fixes**: "fixed by...", "the solution was...", "root cause..."- **Learnings**: "learned that...", "discovered...", "turns out..."- **Architecture**: "created...", "implemented...", "refactored..."- **Preferences**: "always...", "never...", "prefer to..."- **Notes**: "important:", "remember:", "key point..."Don't rely solely on auto-extraction. Use `remember` proactively for important events.---> Source: [mkdelta221/claude-cortex](https://github.com/mkdelta221/claude-cortex) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Memory