qdrant-memory
Installation
SKILL.md
Qdrant memory
Use for durable memory recall/explicit edits, destination maintenance or Mem0 migration from any agent with compatible MCP tools or command execution. The shared runtime owns embedding, storage, scope, ledger and recovery. Hermes additionally supplies its automatic extraction/prefetch lifecycle.
Choose the workflow
Read only the reference needed for the request:
| Request | Reference | Required interface |
|---|---|---|
| New local profile, connect an existing Qdrant, back up/exit or troubleshoot | Operator workflows | Standalone Runtime CLI for setup/doctor/export; the plugin MCP server exposes only scoped memory tools |
| Search/save facts, replace/delete by exact ID, inspect provenance | Usage | Scoped MCP/Hermes qdrant_memory_* tools or standalone CLI |
| Status, diagnostics, inventory/export, authorized retry/scope deletion | Maintenance | Standalone qdrant-memory --home PROFILE or existing Hermes CLI |
| Adopt an existing destination onto the 0.7.1 Qdrant policy | Operator workflows | Operator CLI upgrade plan/apply/resume/status; never exposed through MCP |
| Mem0 JSON/collection dry-run, import, resume/retry-failed, verification | Migration | Selected CLI's migrate mem0 command |
| Codex native v1/v2 inspection, migration, handoff or Owner candidate events | Codex portability | Runtime CLI and, for Owner events, a separately verified adapter |