skills/remembering-conversations/SKILL.md
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.
npx skillsauth add obra/episodic-memory remembering-conversationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Core principle: Search before reinventing. Searching costs nothing; reinventing or repeating mistakes costs everything.
YOU MUST search historical memory for any historical search.
Announce: "Searching past conversations for [topic]."
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"
If a search-conversations agent is available, dispatch it with the same prompt. If not, use the MCP tools directly:
search toolread toolThe search workflow will:
search toolread toolSaves 50-100x context vs. loading raw conversations.
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:
When you're stuck:
When historical signals are present:
Before answering from uncertainty:
Don't search first:
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__readWhen 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.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
data-ai
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.