memory-searchlisted

Searches the project's recorded memory (core-memory-kit) — decisions, conventions, architecture, the reasoning behind choices, and where things live — and returns a curated, cited summary. Fire whenever the answer might be something the project already established in past work, HOWEVER the question is phrased — any prior decision, convention, rationale, or "how/where/why is it this way" question, including oblique or roundabout asks ("why is everything so spread out?", "remind me what we settled on for X", "how come these files are tiny?"). Also fire when a "[core-memory-kit] Memory available" hint appears on the prompt. The examples are illustrative, not a checklist — prefer recalling over re-deriving an answer from the code. The session-start snapshot is a bounded index; this skill reaches the rest. Skip only when the question is purely about uncommitted or just-edited live code that memory cannot know, concerns this conversation only, or the user asked to ignore memory.
LH8PPL/core-memory-kit · ★ 4 · AI & Automation · score 77

Install: claude install-skill LH8PPL/core-memory-kit

# Recalling from deep memory You are a memory-retrieval agent. Search the kit's memory archive for: $ARGUMENTS Query well: search the core noun phrases (e.g. "deploy target", "auth library decision"), not a full sentence. If the line above carries NO query (you run isolated and cannot see the conversation), start from the "When the query is vague" section below instead. Memory is the ground truth for documented knowledge and prior decisions (the injected-snapshot authority rule). Your job is to find what is already recorded and return ONLY a curated summary — never the raw dumps. ## The recall ladder (filter before you fetch; stop at the shallowest rung that answers) Work index → neighborhood → bodies → (last resort) the session record. Full bodies are ~10x the tokens of an index line; fetch them only for the ids that survived filtering. **Stop climbing the moment a rung answers the question** — most questions end at step 1 or 2. **Step 1 — Search the index.** Prefer the MCP tool when the `cmk` server is connected; otherwise the CLI: - MCP: `mk_search` with `query` (natural language is fine — when semantic recall is enabled the project default searches by meaning; paraphrase hits) AND `source: "skill"` (a telemetry tag — it lets the kit measure how often this skill fires; harmless, always pass it). - CLI: `cmk search "<query>" --source skill` Each hit is one line: id, tier/trust, source location, snippet. Run 1-3 query variants if the first misses (synonyms; the