qmd-memory

Run local hybrid searches with BM25, embeddings, and LLM re-ranking.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/xintuchain/tongtong --skill qmd-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qmd-memory
Source: https://github.com/xintuchain/tongtong/tree/main/skills/qmd-memory
Command: npx skills add https://github.com/xintuchain/tongtong --skill qmd-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @tobilu/qmd, bc, and includes scripts (resource) components.

What problem does it solve?

QMD Memory eliminates recurring API costs and latency caused by remote memory and embedding lookups by running hybrid search locally and serving semantic context to OpenClaw agents.

Core Features & Use Cases

  • Local hybrid search combining BM25 (SQLite FTS5), local vector embeddings, and LLM re-ranking to return high-quality context without external API calls.
  • Auto-configured collections & context that index workspace files, daily logs, intelligence, and project documents to make retrieval precise and relevant.
  • Nightly indexing and multi-agent support with optional MCP server to share a single memory index across multiple agents for collaborative workflows.
  • Use case: a team of agents querying past decisions, research, and daily logs for planning meetings while avoiding embedding API charges and keeping data local.

Quick Start

Run the OpenClaw skill setup to install QMD, configure collections, and generate local embeddings for your workspace.

Frequently Asked Questions about qmd-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run local hybrid search for agent memory without paying API costs?

You can eliminate recurring API memory search costs by performing local hybrid searches using QMD, which combines BM25 SQLite FTS5 indexing, local vector embeddings, and LLM re-ranking to retrieve context without external API calls.

How does local hybrid search work for retrieving semantic context?

Local hybrid search works by combining BM25 keyword matching through SQLite FTS5, local vector embeddings for semantic similarity, and LLM re-ranking to return high-quality context from indexed collections.

Do I need a Node.js environment to use local embeddings for memory indexing?

Yes, a Node.js environment is required to generate local embeddings and run the QMD memory indexing process for your workspace, daily logs, and project collections.

Can I share a single memory index across multiple agents for collaborative workflows?

Yes, you can share a single memory index across multiple agents by enabling the optional MCP server, which supports multi-agent sharing and collaborative querying of past decisions and research.

What is the best way to index workspace files and daily logs for agents locally?

The best way to index workspace files, daily logs, intelligence, and project documents is using the nightly indexing feature, which auto-configures collections and generates local embeddings for precise retrieval.

Why does remote memory lookup cause latency and how to avoid it?

Remote memory lookup causes latency through external network requests and embedding API charges, which you can avoid by running local hybrid search and serving semantic context directly to OpenClaw agents.