Nowledge Community — скилл

---
name: search-memory
description: Search Nowledge Mem memories and prior threads for past decisions, procedures, and context with normal, deep, or progressive retrieval; automatically show a focused graph of successful Memory results.
---

# Search Memory

> AI-powered search across your personal knowledge base using Nowledge Mem.

## When to Use

**Strong signals — search when:**

- the user references previous work, a prior fix, or an earlier decision
- the task resumes a named feature, bug, refactor, incident, or subsystem
- the task is a review, regression, release, docs-alignment, or connector-behavior question
- a debugging pattern resembles something solved earlier
- the user asks for rationale, preferences, procedures, or recurring workflow details
- the user uses implicit recall language: "that approach", "like before", "the pattern we used"

**Contextual signals — consider searching when:**

- complex debugging where prior context would narrow the search space
- architecture discussion that may intersect with past decisions
- domain-specific conventions the user has established before
- the current result is ambiguous and past context would make the answer sharper

## Retrieval Routing

Prefer the host's Nowledge Mem MCP tools when exposed: `memory_search` for
durable knowledge, `thread_search` for past conversations, and
`thread_fetch_messages` for inspecting a matching conversation. Otherwise:

1. Start with `nmem --json m search "query" -n 5` for durable knowledge.
2. Use `nmem --json t search "query" --limit 5` for a prior conversation or exact session history.
3. If a result includes `source_thread`, inspect it once for the specific messages needed with `nmem --json t show <thread_id> --limit 8 --offset 0 --content-limit 1200`.
4. Prefer the smallest retrieval surface that answers the question.

For continuation-heavy engineering work, search near the start of the task. Do not wait for the user to literally ask for memory search.

Keep the configured endpoint, owner, agent identity, and active space. If the
runtime already knows an active lane, pass that scope through the supported
MCP parameters or add `--space "<space name>"` to CLI commands. Never infer a
space from the current folder or switch owners or spaces to find more results.

## Retrieval Modes

- **Normal (default)**: use `memory_search` with `mode="normal"`, or
  `nmem --json m search "query" --mode normal -n 5`, for concrete facts and
  bounded recall.