Search Memory

nowledge-co/community/nowledge-mem-droid-plugin/skills/search-memory

by nowledge-co1f4d7eb61466dbfc93ce8d7a0a806c4d4a196dd0No licenseListed Oct 9, 2026Updated Oct 9, 2026

Search memory and thread history when past knowledge would materially improve the answer. Route between distilled memories and prior discussions instead of treating them as separate silos.

Instructions onlyAI & Agents
AI-generated overview

Guides an agent to search stored memories and past thread history when prior context would improve an answer.

What it does
This skill provides instructions for deciding when to retrieve durable memories or earlier conversation threads before answering. It lists strong and contextual search signals, gives commands for memory and thread search plus progressive thread fetching, and defines a response contract for disclosing recalled knowledge. It produces guidance and retrieval behavior rather than files or code.
When to use it
Use it when a task connects to prior work, resembles something solved earlier, involves reviews, regressions, releases, docs alignment, or connector behavior, or when the user asks why a decision was made. It also fits implicit recall language such as "that approach" or "like before". Skip it for fundamentally new tasks, generic syntax questions, or when the user wants a fresh perspective.
Requirements
Requires the nmem command-line tool with memory and thread search subcommands, plus access to the underlying memory and thread stores. No scripts are shipped; the skill is instructions only.

Search Memory

When to Search

Strong signals — search when:

  • the current task connects to prior work
  • the bug or design resembles something solved earlier
  • the task is a review, regression, release, docs-alignment, or connector-behavior question
  • the user asks why a decision was made
  • a previous discussion or session likely contains the missing context
  • the user uses implicit recall language: "that approach", "like before"

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

Skip when:

  • the task is fundamentally new
  • the question is generic syntax or reference material
  • the user explicitly wants a fresh perspective

Tool Usage

Start with durable knowledge:

bash
nmem --json m search "3-7 core concepts"

Use thread search when the user is really asking about a prior conversation:

bash
nmem --json t search "query" --limit 5

If a memory result includes source_thread, or thread search identifies the likely discussion, fetch progressively:

bash
nmem --json t show <thread_id> --limit 8 --offset 0 --content-limit 1200

Increase --offset only when more messages are actually needed.

Response Contract

  • Be explicit when you relied on recalled knowledge
  • Prefer the smallest retrieval surface that answers the question
  • Suggest distillation only if the current discussion produced new durable knowledge
  • For continuation-heavy engineering work, search near the start of the task rather than waiting for an explicit recall request

Source and attribution

Source:nowledge-co/communityinnowledge-mem-droid-plugin/skills/search-memoryat commit1f4d7eb

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal