← ClaudeAtlas

ariadnelisted

Mandatory long-term memory workflow for Codex, Claude Code, and MCP clients backed by the local Ariadne server (Qdrant + bge-m3). Always use at the start or resumption of substantive project work, after context compaction, when prior work or decisions may matter, and immediately after durable decisions, gotchas, completed reports, release/deployment results, or verified status. Also use for explicit remember, recall, or Ariadne requests.
mclaut/ariadne · ★ 3 · AI & Automation · score 74
Install: claude install-skill mclaut/ariadne
# Ariadne — long-term memory Ariadne is a local, multilingual, hybrid-search memory server (MCP). If it is registered, you have five tools: `mcp__ariadne__memory_recall`, `mcp__ariadne__memory_save`, `mcp__ariadne__memory_delete` and `mcp__ariadne__memory_move`, plus `mcp__ariadne__credential_access` for a separate human approval handshake before cross-project credential use. The runtime lives in `~/.ariadne/` (binaries, Qdrant data, backups, logs); source lives in the repo. ## Recall — when and how - **Start of substantive work in a project**: recall the project's context once (`query: "<project name> current state decisions", wing: "<stable-project-slug>"`). Don't recall for trivial one-liners. Every semantic recall MUST include the active project's `wing`; Ariadne rejects an unscoped semantic query. - **The user references the past**: "what did we decide", "why did we choose", "як ми робили" → recall BEFORE answering from your own guesses. - Queries are multilingual — query in ANY language, memories in any language will match (bge-m3 is cross-lingual; scores ≥0.6 are usually relevant). - Prefer 2–3 focused recalls over one vague one. `limit` default 5 is fine. - Project scope is default-deny. Never omit `wing` to "see what matches" and never substitute another project's wing. When the user explicitly requests cross-project knowledge, call recall with the active `wing`, `all_wings: true`, and a concise `purpose`. Ariadne returns a request id without searc