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. Also use when you see '[memsearch] Memory available' hints.
Install this agent skill to your Project
npx add-skill https://github.com/zilliztech/memsearch/tree/main/plugins/codex/skills/memory-recall
SKILL.md
You are performing memory retrieval for memsearch. Search past memories and return the most relevant context to the current conversation.
Project Collection
Determine the collection name by running:
bash __INSTALL_DIR__/scripts/derive-collection.sh
Steps
-
Search: Run
memsearch search "<query>" --top-k 5 --json-output --collection <collection name from above>to find relevant chunks.- If
memsearchis not found, tryuvx memsearchinstead. - Choose a search query that captures the core intent of the user's question.
- If
-
Evaluate: Look at the search results. Skip chunks that are clearly irrelevant or too generic.
-
Expand: For each relevant result, get the full context using one of these methods:
- Primary: Run
memsearch expand <chunk_hash> --collection <collection name from above>to get the full markdown section. - Fallback (if expand fails with a lock/permission error due to sandbox): Read the source file directly. The search results include
source(file path) andstart_line/end_line— usecat <source_file>or read the relevant line range to get the full context. This avoids the Milvus lock file issue.
- Primary: Run
-
Deep drill (optional): If an expanded chunk contains transcript anchors (HTML comments with session/rollout info), and the original conversation seems critical:
- Run
bash __INSTALL_DIR__/scripts/parse-rollout.sh <rollout_path>to retrieve the original conversation turns. - If the anchor format is unfamiliar (e.g.
transcript:+turn:,db:instead ofrollout:), try reading the referenced file directly to explore its structure and locate the relevant conversation by the session or turn identifiers in the anchor.
- Run
-
Return results: Output a curated summary of the most relevant memories. Be concise — only include information that is genuinely useful for the user's current question.
Output Format
Organize by relevance. For each memory include:
- The key information (decisions, patterns, solutions, context)
- Source reference (file name, date) for traceability
If nothing relevant is found, simply say "No relevant memories found."
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
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.
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.
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.
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.
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.
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.
Didn't find tool you were looking for?