360 Secure SkillHub
360 安全技能中心

Remembering Conversations

在理解当前任务后,按需派发 search-conversations 搜索代理,检索并读取相关历史会话,综合出决策、模式与注意事项,减少重复劳动和重复错误;也支持直接使用 MCP 搜索与读取工具。

yumoezhung
yumoezhung
热度 86.68
最近更新 2026-05-11 17:28:46
分类:知识依赖:MCP 服务 / 内部调用大模型应用场景:研究 / 摘要总结

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add remembering-conversations
Metadata
name
remembering-conversations
description
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.

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.