remembering-conversations
Skill487 starsChanged 6 months agoMITView on GitHub
You MUST invoke this skill before saying "I don't know," guessing, or treating any topic as new, no matter how trivial the question seems. It supplements other memory systems, which only hold partial records. Searching past conversations is the only way to recover what was actually said.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- PracticalSwan/agent-skillstheir own version, first seen Oct 19, 2026
- robertn702/opencode-episodic-memorytheir own version, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- PracticalSwan/agent-skills★ 22same name
- robertn702/opencode-episodic-memory★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 7 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Core principle: Search before reinventing.
- Very specific: line 18
Use the Task tool with subagent_type: "search-conversations":
- Very specific: line 29
If a search-conversations agent is available, dispatch it with the same prompt.
- Very specific: line 31
Search with the episodic-memory search tool
- Very specific: line 32
Read the top 2-5 results with the episodic-memory read tool
- Very specific: line 37
Search with the search tool
- Very specific: line 38
Read top 2-5 results with the read tool
- Distinctive: line 46
Use the MCP tools directly unless a local search agent is available:
- Distinctive: line 55
Use this whenever the current task would benefit from information you may have learned before, even if the user did not explicitly ask you …
- Distinctive: line 73
Before guessing from memory or saying "I don't know" about something that may have been learned in a past conversation, search memory …
- Distinctive: line 78
Before understanding what you're being asked to do
- Distinctive: line 82
Use these directly when a search agent is unavailable or the current harness does not support agent dispatch:
- Distinctive: line 86
When using MCP tools directly, keep context small: search first, then read only the top 2-5 relevant conversations or line ranges.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Remembering Conversations
Core principle: Search before reinventing. Searching costs nothing; reinventing or repeating mistakes costs everything.
Mandatory: Search Historical Memory
YOU MUST search historical memory for any historical search.
Announce: "Searching past conversations for [topic]."
Claude Code
Use the Task tool with subagent_type: "search-conversations":
Task tool:
description: "Search past conversations for [topic]"
prompt: "Search for [specific query or topic]. Focus on [what you're looking for - e.g., decisions, patterns, gotchas, code examples]."
subagent_type: "search-conversations"Codex
If a search-conversations agent is available, dispatch it with the same prompt. If not, use the MCP tools directly:
- Search with the episodic-memory
searchtool - Read the top 2-5 results with the episodic-memory
readtool - Synthesize findings in your response
- Include source pointers so the user can inspect the original conversations
The search workflow will:
- Search with the
searchtool - Read top 2-5 results with the
readtool - Synthesize findings (200-1000 words)
- Return actionable insights + sources
Saves 50-100x context vs. loading raw conversations.
opencode
Use the MCP tools directly unless a local search agent is available:
- Search with the episodic-memory
searchtool - Read the top 2-5 results with the episodic-memory
readtool - Synthesize findings in your response
- Include source pointers so the user can inspect the original conversations
When to Use
Use this whenever the current task would benefit from information you may have learned before, even if the user did not explicitly ask you to search.
When past experience may help:
- You need to recall decisions, rationale, patterns, solutions, pitfalls, or project context from earlier work
- A task resembles something you've solved, debugged, reviewed, released, or planned before
- You need to repeat a workflow or process that may have prior gotchas or established steps
When you're stuck:
- You've investigated a problem and can't find the solution
- Facing a complex problem without obvious solution in current code
- Need to follow an unfamiliar workflow or process
When historical signals are present:
- User says "last time", "before", "we discussed", "you implemented"
- User asks "why did we...", "what was the reason..."
- User says "do you remember...", "what do we know about..."
Before answering from uncertainty:
- Before guessing from memory or saying "I don't know" about something that may have been learned in a past conversation, search memory unless the current conversation already answers it
Don't search first:
- For current codebase structure (use Grep/Read to explore first)
- For info in current conversation
- Before understanding what you're being asked to do
Direct MCP Tool Access
Use these directly when a search agent is unavailable or the current harness does not support agent dispatch:
mcp__plugin_episodic-memory_episodic-memory__searchmcp__plugin_episodic-memory_episodic-memory__read
When using MCP tools directly, keep context small: search first, then read only the top 2-5 relevant conversations or line ranges.
See MCP-TOOLS.md for complete API reference if needed for advanced usage.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

