agentsclimarketplace

Remembering conversations

Skill aiskillstore/marketplace/skills/obra/remembering-conversations

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.From its SKILL.md

Install
npx -y skills add aiskillstore/marketplace --skill remembering-conversations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.5 KB, 512 tokens by cl100k_base, as published. Nobody here has run it

Remembering Conversations

Core principle: Search before reinventing. Searching costs nothing; reinventing or repeating mistakes costs everything.

Mandatory: Use the Search Agent

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:

  1. Search with the search tool
  2. Read top 2-5 results with the show tool
  3. Synthesize findings (200-1000 words)
  4. Return actionable insights + sources

Saves 50-100x context vs. loading raw conversations.

When to Use

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:

  • User asks "how should I..." or "what's the best approach..."
  • You've explored current codebase and need to make architectural decisions
  • User asks for implementation approach after describing what they want

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..."

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 Tool Access (Discouraged)

You CAN use MCP tools directly, but DON'T:

  • mcp__plugin_episodic-memory_episodic-memory__search
  • mcp__plugin_episodic-memory_episodic-memory__show

Using these directly wastes your context window. Always dispatch the agent instead.

See MCP-TOOLS.md for complete API reference if needed for advanced usage.

What ships with it: 2 files

23.5 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.