docs(openclaw): add troubleshooting for slot default and concurrent agents

OpenClaw 3.22 introduced implicit memory-slot defaulting to memory-core.
Users who upgrade or install manually may lose the explicit slot setting,
causing only memory_search/memory_get to register. Added troubleshooting
sections to README and slot verification step to setup SKILL.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: wey-gu

nowledge-mem-openclaw-plugin/README.md

@@ -433,6 +433,40 @@ If OpenClaw logs a warning like `plugins.allow is empty; discovered non-bundled
 
 If you also use linked or workspace copies, review `plugins.load.paths` before relying on an allowlist. OpenClaw allowlists plugin ids, not install provenance.
 
+## Troubleshooting
+
+**Only `memory_search` and `memory_get` show up — saves go to local markdown files**
+
+The memory slot is probably still set to the built-in `memory-core`. OpenClaw 3.22+ defaults to `memory-core` when no explicit slot is configured. Reinstall to reset the slot automatically:
+
+```bash
+openclaw plugins install @nowledge/openclaw-nowledge-mem
+```
+
+Or set the slot manually in `~/.openclaw/openclaw.json`:
+
+```json
+{
+  "plugins": {
+    "slots": { "memory": "openclaw-nowledge-mem" }
+  }
+}
+```
+
+Restart OpenClaw after either change.
+
+**Search timeouts with many concurrent agents**
+
+When running many agents in parallel, all searches share a single database connection. Upgrade to Nowledge Mem v0.6.12+ (backend) so scoring writes no longer block search responses.
+
+**`nmem --json status` fails in local mode**
+
+The Nowledge Mem backend is not running. Start it from the desktop app, or run the backend manually.
+
+**Remote mode not connecting**
+
+Check `~/.nowledge-mem/config.json` credentials. Run `nmem --json --api-url "$URL" status` to verify the server is reachable.
+
 ## What Makes This Different
 
 - **Local-first**: no API key, no cloud account. Your knowledge stays on your machine.

nowledge-mem-openclaw-plugin/SKILL.md

@@ -186,6 +186,18 @@ First check the plugin status:
 openclaw nowledge-mem status
 ```
 
+If only `memory_search` and `memory_get` tools are available (other Nowledge Mem tools missing), the memory slot may still point to the built-in `memory-core`. Verify the slot in `~/.openclaw/openclaw.json`:
+
+```json
+{
+  "plugins": {
+    "slots": { "memory": "openclaw-nowledge-mem" }
+  }
+}
+```
+
+If missing, reinstall (`openclaw plugins install @nowledge/openclaw-nowledge-mem`) which sets the slot automatically. This is common after upgrading OpenClaw to 3.22+ where the default memory slot changed.
+
 Then verify in chat.
 
 For a clean synthetic check: