Use when user asks 'how should I...' or 'what's the best approach...' after exploring code, OR when you've tried to solve something and are stuck, OR for unfamiliar workflows, OR when user references past work. Searches conversation history.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
MCP-TOOLS.mdCore principle: Search before reinventing. Searching costs nothing; reinventing or repeating mistakes costs everything.
YOU MUST dispatch the search-conversations agent for any historical search.
Announce: "Dispatching search agent to find [topic]."
Then 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"
The agent will:
search toolshow toolSaves 50-100x context vs. loading raw conversations.
You often get value out of consulting your episodic memory once you understand what you're being asked. Search memory in these situations:
After understanding the task:
When you're stuck:
When historical signals are present:
Don't search first:
You CAN use MCP tools directly, but DON'T:
mcp__plugin_episodic-memory_episodic-memory__searchmcp__plugin_episodic-memory_episodic-memory__showUsing these directly wastes your context window. Always dispatch the agent instead.
See MCP-TOOLS.md for complete API reference if needed for advanced usage.