| name | memtrace-docs |
| description | Route Memtrace product documentation questions to the hosted docs MCP tools before guessing, searching the web, or reading stale local copies. Use when the user asks how Memtrace works, how to install/configure CLI/MCP/fleet/Cortex/enterprise MemDB, what tools or skills exist, what a command does, or wants the agent to read up on official docs. Calls search_docs, ask_docs, or read_doc on memtrace.io (override with MEMTRACE_DOCS_API_URL). Do not hallucinate Memtrace behavior — query docs first. Separate from memtrace-first (your repo's code graph). |
Memtrace Docs First
The Iron Law
IF THE USER ASKS ABOUT MEMTRACE PRODUCT DOCS → USE DOCS MCP TOOLS FIRST.
Do not guess CLI flags, MCP tool lists, enterprise deploy steps, or fleet rules
from memory. Query the hosted documentation corpus at memtrace.io (or
MEMTRACE_DOCS_API_URL), then answer with citations.
memtrace-first = your indexed SOURCE CODE (find_code, get_impact, …)
memtrace-docs = official MEMTRACE DOCUMENTATION (search_docs, ask_docs, read_doc)
Docs tools call the hosted Memtrace docs API over HTTPS. They do not read
your local MemDB or your repo. Core graph tools stay offline; docs tools degrade
gracefully when the network is down (ok: false + hint).
Server check (once per session)
Confirm the docs tools are available on your memtrace MCP server:
search_docs — ranked chunks (slug, title, H2, excerpt)ask_docs — grounded Q&A { answer, citations[], refused }read_doc — full page text by slug- Resources:
memtrace://docs/<slug> via read_resource (optional)
If none of these exist, the MCP build may be outdated — tell the user to update
Memtrace and run npx -y memtrace-skills@latest install.
Override API host: MEMTRACE_DOCS_API_URL (default https://memtrace.io).
The decision rule
| User is asking | Right tool | Sub-skill |
|---|
| "How do I install / configure / deploy X in Memtrace?" | ask_docs(question=…) | memtrace-docs-ask |
| "What MCP tools / skills / CLI commands exist?" | ask_docs or search_docs then read_doc on hit slugs | memtrace-docs-ask / memtrace-docs-search |
"What does memtrace rail enable do?" | ask_docs | memtrace-docs-ask |
| "Find docs about fleet coordination" | search_docs(query=…) | memtrace-docs-search |
| "Read the full getting-started page" | read_doc(slug="getting-started") | memtrace-docs-read |
| "Read enterprise MemDB deploy guide" | read_doc(slug="enterprise/memdb-deploy") | memtrace-docs-read |
| Need several related sections | search_docs → read_doc on top slugs | memtrace-docs-search + memtrace-docs-read |
Default for natural-language questions: ask_docs — it retrieves context and
returns a cited answer in one call.
Default for "find the doc about…": search_docs — scan chunks, then read_doc
if you need the full page.
Standard workflows
"How does X work in Memtrace?" (most common)
ask_docs(question="<user question verbatim>")- If
refused: true or ok: false → search_docs with shorter keywords → read_doc on best slug
- Quote the answer; link slugs as
/docs/<slug> when helpful
- If docs say "not found", say so — do not invent flags or behavior
"What tools / commands / skills are available?"
ask_docs(question="What MCP tools are available?") or fleet/skills variant- If the answer lists categories but user wants exhaustive detail →
read_doc(slug="mcp/tools")
- For agent skills →
read_doc(slug="mcp/skills")
"Read up on X before we implement"
search_docs(query="X", limit=8)read_doc(slug=<top hit>) for each page you will rely on- Summarize with citations; use
memtrace-first only when switching to their repo's code
Enterprise / self-hosted MemDB
ask_docs(question="How do I deploy MemDB with Helm on Azure?") or user wording- Follow-up
read_doc(slug="enterprise/memdb-deploy") for operator steps
- Engineer connect →
read_doc(slug="enterprise/connect") or cli/connect
Red flags — STOP, use docs tools
| Thought | Reality |
|---|
| "I know how Memtrace fleet works from training data" | Product docs change — ask_docs first |
| "I'll grep the repo for README" | User repo ≠ official docs — use search_docs / read_doc |
| "I'll web-search Memtrace" | Use hosted docs API — same corpus as memtrace.io/docs |
ask_docs returned refused: true | Docs corpus had no match — say so; try search_docs with different terms |
ok: false network error | Report offline; core Memtrace graph tools still work locally |
Relationship to other skills
| Skill | When |
|---|
memtrace-docs | Questions about Memtrace product (install, MCP, fleet, Cortex, enterprise) |
memtrace-first | Questions about the user's indexed source code |
memtrace-decision-memory | Why code exists (Cortex decisions) — not product docs |
Use both when needed: docs for "how is Memtrace supposed to work?", graph tools for
"how does this repo implement it?"
Output
Prefer citing doc slugs returned in citations or search_docs results:
ask_docs → { ok: true, answer: "…", citations: ["cli/rail", "mcp/skills"], refused: false }
search_docs → { ok: true, results: [{ slug, pageTitle, h2Title, excerpt }] }
read_doc → { ok: true, slug, title, body }
When refused: true, tell the user the docs did not cover it and suggest browsing
https://memtrace.io/docs or rephrasing.
Sub-skills
- Discovery / chunk search →
memtrace-docs-search
- Grounded Q&A →
memtrace-docs-ask
- Full page read →
memtrace-docs-read
