From mneme
Use when the user asks a factual question whose answer might live in the vault. Invokes mneme_search (FTS5 BM25, optionally fused with dense and KG backends in standard and full profiles).
How this skill is triggered — by the user, by Claude, or both
Slash command
/mneme:mneme-searchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user asks a question that sounds like recall from prior
When the user asks a question that sounds like recall from prior work or notes, search the vault first instead of guessing.
/mneme:search directly (when that surface exists).Call the mneme_search MCP tool with:
query: the user's question in natural language.top_k: 5 by default. Raise to 10 only when the user asks for a
broad sweep.filters.date_from / filters.date_to when the user
scopes their question to a specific time window.Inspect the returned hits. Each has path, title, snippet,
and a relevance score. Read the snippets first. If they answer
the question, cite the path and reply. If they only partially
answer, follow up with mneme_recall on the most promising paths
to pull the full body.
npx claudepluginhub onourimpram/mneme --plugin mnemeGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.