feat(plugins): share native session handoff and soften memory search

integrations/opencode-plugin/opencode-skills/mem0-context-loader/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mem0-context-loader
-description: Searches and injects relevant memories into context before starting work on a task. Use when beginning a new task, switching context, or when project history, past decisions, or coding conventions need to be loaded.
+description: Search earlier context when project history, decisions, or preferences could help with a specific question.
 ---
 
 # Context Loader
@@ -9,23 +9,14 @@ Pre-fetches relevant memories to prime context before working on a task.
 
 ## When to use
 
-- Session start (invoke manually or auto-triggered by skill description matching)
-- User starts work on a specific feature or file set
-- Complex multi-step task begins
-- User says "what do we know about X" or "context for X"
+Use when earlier work could explain a decision, fix, command, or preference you
+need. Skip this skill when the context already answers the question.
 
 ## Steps
 
 1. **Extract topics** from current message/task. Identify: file paths, module names, feature areas, error patterns.
 
-2. **Run 2-4 parallel `search_memories` calls** with different angles:
-
-   | Query angle | Filter | Purpose |
-   |---|---|---|
-   | Feature/module name | `{"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}, {"metadata": {"type": "decision"}}]}` | Architecture decisions |
-   | File paths mentioned | `{"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}, {"metadata": {"type": "convention"}}]}` | Coding patterns |
-   | Error keywords (if any) | `{"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}, {"metadata": {"type": "anti_pattern"}}]}` | Known pitfalls |
-   | Broad project context | `{"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}` | Catch-all |
+2. **Search one focused question** using `search_memories`. Keep the default project scope. Search again only if a specific gap remains.
 
 3. **Deduplicate** results by memory ID across all search responses.
 

integrations/opencode-plugin/opencode-skills/mem0-search/SKILL.md

@@ -27,10 +27,9 @@ When an ID is detected:
 
 ### Step 2: Search
 
-Run 2 parallel `search_memories` calls:
-
-1. Broad: `query=<user's query>`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`, `rerank=true`
-2. Targeted: `query=<user's query>`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}, {"metadata": {"type": "decision"}}]}`, `top_k=5`, `rerank=true`
+Call `search_memories` with `query=<user's query>`,
+`filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`.
+Search again only if a specific gap remains.
 
 ### Step 3: Display
 

integrations/opencode-plugin/opencode-skills/mem0-tour/SKILL.md

@@ -36,9 +36,7 @@ If `--all-projects` is NOT present, use the standard single-project flow below.
 When `/mem0-tour` receives a search query argument (e.g., `/mem0-tour auth middleware`)
 WITHOUT `--all-projects`, run in **peek mode** — compact one-liner results:
 
-1. Run 2 parallel `search_memories` calls:
-   - Broad: `query=<query>`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`, `rerank=true`
-   - Targeted: `query=<query>`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}, {"metadata": {"type": "decision"}}]}`, `top_k=5`, `rerank=true`
+1. Call `search_memories` with `query=<query>`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`. Search again only if a specific gap remains.
 2. Deduplicate by ID, display compact results:
    ```
    ## mem0 search: "<query>" (<N> results)
@@ -60,15 +58,10 @@ Call `get_memories` to fetch all memories for this project:
 
 `filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": "<active_project_id>"}]}`, `page_size=100`
 
-### Step 2: Run supplementary semantic searches
+### Step 2: Check coverage
 
-In parallel, run these `search_memories` calls to get relevance-ranked results for key topics:
-
-- `query="architecture decisions design choices"`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`, `rerank=true`
-- `query="bugs errors failures anti-patterns"`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`, `rerank=true`
-- `query="project setup tooling conventions preferences"`, `filters={"AND": [{"user_id": "<id>"}, {"app_id": "<pid>"}]}`, `top_k=10`, `rerank=true`
-
-**Do NOT filter by `metadata.type` in these calls.** The platform auto-assigns `categories` — filtering on `metadata.type` misses memories that were auto-categorized but don't have an explicit `metadata.type`.
+Use the fetched memories for the tour. If the user asks about a specific topic
+that the results do not cover, search that question with the same project filters.
 
 ### Step 3: Merge and group