From memtomem
Set up and verify a first memtomem memory source. Use for onboarding, choosing an index path, or confirming that search works.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memtomem:setupThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `$ARGUMENTS` as the memory source path.
Use $ARGUMENTS as the memory source path.
If the request does not clearly specify the memory source path, ask before calling a tool.
mem_status and treat the default provider=none BM25-only configuration as healthy.cd <project-root> && when the setup is project-specific. Retry only after the user completes that explicit trust step.mem_index on that path with force=false and auto_tag=false. This is a one-shot index and must not silently register a watcher root.mem_search to verify retrieval.Do not install Ollama, enable automation hooks, or edit host instruction files unless the user separately requests those actions.
npx claudepluginhub memtomem/memtomem --plugin memtomemSets up @tobilu/qmd for semantic search over mnemonic memories: registers collections from MNEMONIC_ROOT, builds indexes with qmd update, generates embeddings. One-time per-machine bootstrap.
Initializes, repairs, or checks Mem9 memory plugin setup in a Claude Code environment. Verifies Node.js, provisions API keys, and writes auth config.
Diagnoses and configures MemSearch memory behavior for the Claude Code plugin. Handles settings, provider routing, index health, and maintenance of PROJECT.md/USER.md.