Agent skill

memory-recall

Search and recall relevant memories from past sessions. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge.

Stars 1,192
Forks 110

Install this agent skill to your Project

npx add-skill https://github.com/zilliztech/memsearch/tree/main/plugins/openclaw/skills/memory-recall

Metadata

Additional technical details for this skill

openclaw
{
    "emoji": "\ud83e\udde0"
}

SKILL.md

You have three memory tools for progressive recall. Start with search, go deeper only when needed.

Tools (use progressively)

1. memory_search — Start here

Semantic search across all past conversation memories.

  • Returns: chunk summaries with dates, topics, chunk_hash identifiers
  • Use for: "What did we discuss about X?", "Have I asked about Y before?"

2. memory_get — When search results aren't detailed enough

Expands a specific chunk_hash to show the full markdown section with surrounding context.

  • Input: chunk_hash from memory_search results
  • Returns: full section text, may include transcript anchors ()
  • Use for: "Show me the details", "I need more context on that result"

3. memory_transcript — When you need the exact original conversation

Parses the original session transcript to retrieve the raw dialogue.

  • Input: transcript_path from the anchor comment in memory_get results
  • Returns: formatted conversation with [Human]/[Assistant] labels and tool calls
  • Use for: "What exactly did I say?", "Show me the original conversation"
  • If the anchor format is unfamiliar (e.g. rollout:, turn:, db: instead of transcript:), try reading the referenced file directly to explore its structure and locate the relevant conversation by the session or turn identifiers in the anchor.

Decision guide

User intent Tools to use
Quick recall ("did we discuss X?") memory_search only
Need details ("what was the solution?") memory_search → memory_get
Need original dialogue ("show me the exact conversation") memory_search → memory_get → memory_transcript

Tips

  • memory_search returns chunk_hash — pass it to memory_get for expansion
  • memory_get may reveal <!-- session:UUID transcript:PATH --> anchors — pass the path to memory_transcript
  • If memory_search returns no results, try rephrasing with different keywords
  • Results are sorted by relevance (hybrid BM25 + vector search)

Expand your agent's capabilities with these related and highly-rated skills.

zilliztech/memsearch

memory-recall

Search and recall relevant memories from past sessions. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge. Also use when you see '[memsearch] Memory available' hints.

1,192 110
Explore
zilliztech/memsearch

memory-recall

Search and recall relevant memories from past sessions. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge. Also use when you see '[memsearch] Memory available' hints.

1,192 110
Explore
zilliztech/memsearch

memory-recall

Search and recall relevant memories from past sessions. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge.

1,192 110
Explore
davila7/claude-code-templates

verl-rl-training

Provides guidance for training LLMs with reinforcement learning using verl (Volcano Engine RL). Use when implementing RLHF, GRPO, PPO, or other RL algorithms for LLM post-training at scale with flexible infrastructure backends.

23,776 2,298
Explore
davila7/claude-code-templates

openrlhf-training

High-performance RLHF framework with Ray+vLLM acceleration. Use for PPO, GRPO, RLOO, DPO training of large models (7B-70B+). Built on Ray, vLLM, ZeRO-3. 2× faster than DeepSpeedChat with distributed architecture and GPU resource sharing.

23,776 2,298
Explore
davila7/claude-code-templates

gguf-quantization

GGUF format and llama.cpp quantization for efficient CPU/GPU inference. Use when deploying models on consumer hardware, Apple Silicon, or when needing flexible quantization from 2-8 bit without GPU requirements.

23,776 2,298
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results