@yugabytedb/meko-mcp 1.2.0 → 2.0.0

package/assets/skills/meko-mcp-tools-desktop/references/tools-rag-workflow.md

@@ -1,19 +1,16 @@
 # Knowledge Base / RAG workflow
 
-As of 2026-05-07, **knowledge-base ingestion on cloud Meko is a UI-only activity**. The MCP ingestion tools exist but are gated off on cloud and rely on an S3-only worker that has no mechanism to read user-supplied buckets. `knowledgebase_search` is the only KB tool agents can rely on today.
-
-This page tells you which tool to reach for, what's usable where, and where the current gaps are tracked.
+`knowledgebase_search` is the only KB tool exposed via MCP. Index
+creation and ingestion happen out of band — through the **Meko UI**
+(`cloud.mekodata.ai`).
 
 ## Decision table
 
 | Situation | Use this | Why |
 |---|---|---|
-| Search an existing KB | `knowledgebase_search` | The one KB tool that works on cloud Free Tier and prod today |
-| Add documents to a KB on cloud | **Meko UI** — Datapack → Actions menu → **Add Knowledge** | File-upload dialog (PDF/TXT/MD/JSON/MP4, 5MB each, 10/batch). The MCP ingestion path is not usable on cloud |
-| Create a new vector index (self-hosted / paid) | `knowledgebase_trigger_index_creation` | Only works when the ingestion worker has IAM access to the S3 bucket you pass |
-| Add a source to an existing index (self-hosted / paid) | `knowledgebase_add_source_to_index` | Same caveat as above |
-| Poll a build (self-hosted / paid) | `knowledgebase_check_index_status` | Gated on cloud Free Tier |
-| Anything that needs KB lifecycle management (list, delete, rename) | **UI** | No MCP tools for KB lifecycle |
+| Search an existing KB | `knowledgebase_search` | The one KB tool exposed via MCP |
+| Add documents to a KB | **Meko UI** — Datapack → Actions → **Add Knowledge** | File-upload dialog (PDF/TXT/MD/JSON/MP4, 5 MB each, 10/batch). No MCP equivalent |
+| Anything else (list / delete / rename / re-index) | **UI** | No MCP tools for KB lifecycle |
 
 ## knowledgebase_search — the one you'll actually call
 
@@ -27,60 +24,16 @@ knowledgebase_search(
     limit=10)
 ```
 
-Required: `scope`, `query`, `agent_id`, `conversation_id`, `datapack_id`. Unlike the memory tools, `datapack_id` has no default here — you must pass it explicitly. `agent_id` is **ignored for filtering** on this tool (KB results are team-shared on the datapack), but you still pass it — your session's value is fine.
-
-Response shape (verified 2026-05-07 against prod):
-```
-{"results": [], "count": 0}
-```
-
-On a populated KB each result carries chunk content and similarity scores. On an empty or nonexistent KB you get an empty array and `count: 0` — not an error.
-
-## MCP ingestion tools — what actually happens when you call them
-
-This applies to `knowledgebase_trigger_index_creation` and `knowledgebase_add_source_to_index`. Understanding the two-layer architecture is the only way to predict whether a call will succeed.
-
-**MCP layer (`src/tools.py`):** takes `source_uris`, splits on `,`, passes each string to `dist_rag.create_source(<uri>)` with **zero validation**. No scheme check, no reachability probe. Returns `"build_triggered"` immediately.
-
-**Worker layer (`yugabyte-db/python/ai/rag_agent/rag_pipeline/aws_source_processor.py`):** only handles `s3://` URIs. Any other scheme raises `ValueError("Invalid source URI")` inside the worker — **async, never surfaced to the MCP caller**. The S3 crawler is instantiated with no credentials; it relies on boto3's default chain (env vars, IAM role, `~/.aws/credentials` on the worker host). So the worker can only read buckets its own AWS identity has access to.
-
-**Implication:** pointing the MCP tool at a user-owned S3 bucket from cloud will return `"build_triggered"` and silently stall at INIT forever. There is no way for the user to supply AWS credentials through the MCP tool.
-
-## Free-Tier cloud gating (verified 2026-05-07 against `https://mcp.mekodata.ai/mcp`)
-
-| Tool | Verbatim response |
-|---|---|
-| `knowledgebase_trigger_index_creation` | `{"error": "not_available", "detail": "Vector index creation is not available on the free tier."}` |
-| `knowledgebase_add_source_to_index` | Same as above |
-| `knowledgebase_check_index_status` | `{"error": "not_available", "detail": "Index status check is not available on the free tier."}` |
-| `knowledgebase_search` | Works: `{"results": [], "count": 0}` |
-
-`{"error": "not_available"}` is a server-side tier block. Don't retry.
-
-## UI ingestion (cloud Meko) — what the user sees
-
-From `cloud.mekodata.ai`:
-
-1. Open a datapack (`/datapacks/<name>`).
-2. Click **Actions** → **Add Knowledge**.
-3. Drag-and-drop or browse for files. Supported: PDF, TXT, MD, JSON, MP4. Per-file limit 5 MB. Up to 10 files per batch.
-4. The UI handles upload, storage, and index build. The user does not pick a bucket or provide credentials.
-5. Search results from `knowledgebase_search` become available once indexing completes.
-
-If a user asks you "how do I add a document to my knowledge base?", point them at this flow. Do not suggest `knowledgebase_trigger_index_creation` with an S3 URI — on cloud that path does not work.
+Required: `scope`, `query`, `agent_id`, `conversation_id`, `datapack_id`.
+Unlike the memory tools, `datapack_id` has no default here — you must
+pass it explicitly. `agent_id` is **ignored for filtering** on this
+tool (KB results are team-shared on the datapack), but you still pass
+it — your session's value is fine.
 
-## Tracked gaps
-
-- **Upstream GitHub**: [yugabyte/meko-mcp-server#89](https://github.com/yugabyte/meko-mcp-server/issues/89) — disable or gate KB ingestion tools on cloud until the S3 path works end-to-end; return a clearer error than "not_available"; validate schemes at MCP-call time.
-- **Upstream Jira**: MEKO-96 (same issue, cross-linked).
-
-When either lands, the free-tier-gate responses above will change and this page should be revisited.
-
-## Response-shape reference (for agents that need to parse)
-
-### knowledgebase_search
+## Response shape
 
 Populated KB:
+
 ```
 {
   "results": [
@@ -97,38 +50,21 @@ Populated KB:
 }
 ```
 
-Empty or nonexistent KB: `{"results": [], "count": 0}` (no error).
-
-### knowledgebase_trigger_index_creation (when not gated)
-
-Success shape:
-```
-{
-  "source_ids": ["<uuid>", ...],
-  "index_id": "<uuid>",
-  "index_name": "<name>",
-  "status": "build_triggered",
-  "message": "N source(s) registered, index '...' initialised, and build triggered."
-}
-```
-
-Do NOT retry this on failure. Each call creates a new index.
-
-### knowledgebase_add_source_to_index (when not gated)
-
-The historical `r_index_name` vs `r_index_id` parameter-mismatch bug is fixed on main (`src/tools.py` resolves `index_name → index_id` via `SELECT id FROM dist_rag.vector_indexes WHERE index_name = %s` before calling the dist_rag function). If `index_name` doesn't exist you get `{"error": "index_not_found", "detail": "No vector index found with name '...'"}`.
-
-Param is `source_uri` (URI string like `s3://bucket/path/`), **not** `source_id` as older docs may claim.
+Empty or nonexistent KB: `{"results": [], "count": 0}` (no error,
+just an empty array).
 
-### knowledgebase_check_index_status (when not gated)
+## UI ingestion — what the user sees
 
-Returns `pipeline_details` (per-document status) and `pipeline_stats` (aggregated). Check `completion_rate_percent` in `pipeline_stats` and `document_status` in `pipeline_details`.
-
-Stuck at INIT for >5 minutes under self-hosted usually means the worker couldn't reach the bucket — check AWS credentials on the worker host, not the MCP server.
-
-## Prerequisites (self-hosted)
+From `cloud.mekodata.ai`:
 
-- `dist_rag` PostgreSQL extension enabled on the target YugabyteDB database
-- Ingestion workers running (`yugabyte-db/python/ai/rag_agent/`)
-- AWS credentials on the worker host for any S3 bucket you intend to ingest from
-- `datapack_id` passed on every call when targeting a non-default datapack
+1. Open a datapack (`/datapacks/<name>`).
+2. Click **Actions** → **Add Knowledge**.
+3. Drag-and-drop or browse for files. Supported: PDF, TXT, MD, JSON,
+   MP4. Per-file limit 5 MB. Up to 10 files per batch.
+4. The UI handles upload, storage, and index build. The user does not
+   pick a bucket or provide credentials.
+5. Search results from `knowledgebase_search` become available once
+   indexing completes.
+
+If a user asks you "how do I add a document to my knowledge base?",
+point them at this flow.

package/assets/skills/meko-mcp-tools-desktop/references/tools-scope-permissions.md

@@ -1,6 +1,6 @@
 # Scope Permission Hierarchy and Per-Tool Requirements
 
-**WRONG:** `db_run_write_query(scope="read", ...)` → PermissionError: requires 'write' or higher.
+**WRONG:** `memory_add(scope="read", ...)` → PermissionError: requires 'write' or higher.
 **WRONG:** `memory_delete_all(scope="write", ...)` → PermissionError: requires 'admin'.
 
 ## Scope Hierarchy
@@ -17,13 +17,11 @@ Higher scopes include lower scopes. An unrecognized scope string always fails.
 
 ## Per-Tool Requirements
 
-### read scope (11 tools)
+### read scope (9 tools)
 
 | Tool | Group |
 |------|-------|
-| `db_summarize_database` | Database |
-| `db_run_read_only_query` | Database |
-| `knowledgebase_check_index_status` | RAG |
+| `knowledgebase_search` | RAG |
 | `memory_search` | Memory |
 | `memory_get_by_id` | Memory |
 | `memory_get_all` | Memory |
@@ -33,13 +31,10 @@ Higher scopes include lower scopes. An unrecognized scope string always fails.
 | `datapack_list` | Datapack |
 | `datapack_describe` | Datapack |
 
-### write scope (11 tools)
+### write scope (9 tools)
 
 | Tool | Group |
 |------|-------|
-| `db_run_write_query` | Database |
-| `knowledgebase_trigger_index_creation` | RAG |
-| `knowledgebase_add_source_to_index` | RAG |
 | `memory_add` | Memory |
 | `memory_update` | Memory |
 | `memory_delete_by_id` | Memory |
@@ -48,6 +43,7 @@ Higher scopes include lower scopes. An unrecognized scope string always fails.
 | `conversation_update` | Conversation |
 | `datapack_create` | Datapack |
 | `datapack_update` | Datapack |
+| `track_token_usage` | Observability |
 
 ### admin scope (3 tools — destructive, irreversible)
 

package/assets/skills/meko-mcp-tools-desktop/references/tools-troubleshooting.md

@@ -13,7 +13,7 @@ These patterns are extracted from real agent sessions. Follow them to avoid wast
 
 ## Connection errors: "connection already closed"
 
-**Affects:** Memory tools (`memory_add`, `memory_search`, `memory_get_all`) most frequently. DB tools less often.
+**Affects:** Memory tools (`memory_add`, `memory_search`, `memory_get_all`) most frequently.
 
 **Why it happens:** The Python memory subsystem uses a connection cache that doesn't recover from dropped connections (unlike the Go API server which has retry logic with 5 retries and 3-second delays).
 
@@ -21,73 +21,11 @@ These patterns are extracted from real agent sessions. Follow them to avoid wast
 
 1. Retry the same call **once**.
 2. If it fails again, the memory subsystem is unhealthy for this session — stop trying memory calls and tell the user. Do not waste tokens re-sending the same payload.
-3. Direct-SQL fallback **does not apply** on cloud Free Tier (`db_run_read_only_query` returns `{"error": "not_available", "detail": "Free Tier: DB Tools access is not enabled. coming soon."}`). On self-hosted / paid deployments where DB tools are available, inspect memory rows via the multi-tenant schema — tables are namespaced by datapack, not by agent_id. The old `{agent_id}_mem0_collection` per-agent-table layout is gone.
 
 **Anti-pattern from real sessions:** Agent called `memory_add` with 500+ tokens of text, got "connection already closed", retried the identical call 3 more times (each 500+ tokens). Wasted ~2000 tokens on guaranteed failures.
 
 ---
 
-## RAG pipeline stuck at INIT
-
-**Affects:** `knowledgebase_trigger_index_creation` — the build triggers but never completes.
-
-**Symptoms:**
-- `knowledgebase_check_index_status` returns empty `pipeline_details` and `pipeline_stats`
-- Documents remain at `INIT` status indefinitely
-- Work queue tasks are `IN_PROGRESS` with `lease_expires_at` in the past
-
-**Diagnosis:** Query the work queue directly:
-```
-db_run_read_only_query(scope="read",
-    query="SELECT task_type, status, lease_expires_at FROM dist_rag.work_queue WHERE index_name = 'your_index' ORDER BY created_at DESC LIMIT 10")
-```
-
-Look for tasks stuck `IN_PROGRESS` with expired leases — these indicate crashed or hung workers.
-
-**What to do:**
-
-1. Poll status **at most 3 times** with 1-2 minute intervals
-2. If no progress after 3 checks, **stop polling** — the pipeline is stuck
-3. There is **no way to reset or retry stuck tasks via MCP tools**
-4. Creating a new index with a different name (e.g., `_v2`) is a workaround, but if the workers themselves are down, this will also get stuck
-5. Recommend the user check worker logs or restart the pipeline service
-
-**Anti-pattern from real sessions:** Agent created indexes `v1`, `v2`, `v3` — all stuck with the same symptoms. Even making the S3 bucket public didn't help. The issue was worker infrastructure, not permissions.
-
----
-
-## db_run_write_query guardrail error
-
-**Error:** `'dict' object has no attribute 'guardrail_config'`
-
-**Affects:** `db_run_write_query` in some deployments.
-
-**What to do:**
-
-1. Try the call once. If it fails with this specific error, write operations are unavailable in this deployment.
-2. For reads, always use `db_run_read_only_query` (never `db_run_write_query` for SELECT).
-3. Report the issue — it's a server-side bug, not a parameter problem.
-
----
-
-## knowledgebase_add_source_to_index failure
-
-**Error shape:** `{"error": "not_available", "detail": "Vector index creation is not available on the free tier."}`
-
-You're on cloud Free Tier; the ingestion tools are gated off. There is no retry that will succeed. Point the user at the Meko UI's **Add Knowledge** file-upload flow (Datapack → Actions → Add Knowledge) instead.
-
-**Error shape:** `{"error": "index_not_found", "detail": "No vector index found with name '...'"}`
-
-The `index_name` doesn't exist in this datapack's `dist_rag.vector_indexes` table. Either you're targeting the wrong datapack (check `datapack_id`), or the index hasn't been created yet — call `knowledgebase_trigger_index_creation` first.
-
-**Error shape:** tool returns `"build_triggered"` but `knowledgebase_check_index_status` shows documents stuck at `INIT` for >5 minutes.
-
-Most common cause on self-hosted deployments: the worker can't reach the S3 bucket. `S3BucketCrawler()` uses boto3's default credential chain — check `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` / IAM role / `~/.aws/credentials` on the worker host, not on the MCP server. Second cause: the URI isn't `s3://`-prefixed (`aws_source_processor.py` rejects other schemes with `ValueError("Invalid source URI")` async).
-
-**Historical note:** the old `r_index_name` vs `r_index_id` parameter-mismatch bug is fixed on main — the MCP tool now resolves `index_name → index_id` internally via a `SELECT id FROM dist_rag.vector_indexes WHERE index_name = %s` step. Older docs referencing this bug are stale.
-
----
-
 ## Scope parameter errors
 
 **Error:** `Insufficient scope: 'all'. This tool requires 'read' or higher.`
@@ -124,21 +62,6 @@ Pre-existing data may be tagged `"agent"`, `"claude_code"`, `"cursor:<slug>"`, o
 
 ---
 
-## Permission denied on data tables
-
-**Error:** `permission denied for table customer_complaints`
-
-**Why:** The MCP database user may not have read access to all tables, particularly data tables created by the provisioning system within a datapack.
-
-**What to do:**
-
-1. This is a server-side configuration issue — not fixable via MCP tools.
-2. Don't retry. Don't try different query formulations.
-3. Use `db_summarize_database` to see which tables you CAN access.
-4. Report the permission gap to the Meko admin.
-
----
-
 ## Safe-to-retry vs not
 
 | Tool | Safe to retry? | Why |
@@ -147,9 +70,6 @@ Pre-existing data may be tagged `"agent"`, `"claude_code"`, `"cursor:<slug>"`, o
 | `memory_add` | Yes (once) | Mem0 has dedup logic |
 | `memory_update` | Yes (once) | Overwrites same ID |
 | `memory_delete_by_id` | Yes | Deleting already-deleted is a no-op |
-| `db_run_write_query` (INSERT) | **No** | May double-insert rows |
-| `db_run_write_query` (CREATE TABLE) | **No** | "Table already exists" error |
-| `knowledgebase_trigger_index_creation` | **No** | Creates duplicate indexes |
 | `conversation_create` | **No** | Creates duplicate conversations |
 | `conversation_add_message` with `seed` | Yes | Seed-based dedup prevents duplicates |
 | `conversation_add_message` without `seed` | **No** | Creates duplicate messages |

package/assets/skills/meko-select-datapack-desktop/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: meko-select-datapack-desktop
+description: >-
+  Lists the user's Meko datapacks, shows authorization, supports search and
+  pagination, and pins one as the active datapack on Claude Desktop. Triggers
+  when the user says things like "switch datapack", "use datapack <name>",
+  "list my datapacks", "which datapack am I on", "pin <name>", or any request
+  to change or inspect the active datapack. Persistence is via memory_add
+  (Desktop has no SessionStart hook), so the pin survives across sessions
+  until the user clears it.
+license: MIT
+metadata:
+  author: Meko
+  version: "1.1.0"
+  tags: meko, datapack, selection, project, claude-desktop, desktop
+---
+
+# meko-select-datapack-desktop — Pin a datapack for Claude Desktop
+
+Claude Desktop has no SessionStart hook, so the Claude Code variant's sidecar/hook design doesn't apply here. Instead, the pin is stored as a **memory** with a structured tag, scoped to `agent_id="claude_desktop"` (Desktop's project bucket), and you re-read it on every Desktop turn before issuing Meko MCP tool calls. The pin outlives a single Desktop conversation — it sticks until the user explicitly clears it. Same project-scoped semantic as the Claude Code variant; different mechanism.
+
+## How persistence works (Desktop)
+
+A single memory under `agent_id="claude_desktop"` carries the pin:
+
+```
+text:        "meko_active_datapack=<uuid> name=<name> selected_at=<iso8601>"
+metadata:    { "type": "active-datapack-pin" }
+```
+
+You discover it by calling `memory_search(query="meko_active_datapack", agent_id="claude_desktop", limit=1)` at the start of any turn that's about to make a Meko MCP write. If you find a pin, pass `datapack_id="<uuid>"` to every Meko call that accepts it. If you don't find one, fall back to the server default (omit the parameter).
+
+## When to invoke this skill
+
+Trigger immediately on any of these signals:
+
+- User says "switch datapack", "change datapack", "use datapack X", "select datapack", "pick a datapack".
+- User says "list my datapacks", "what datapacks do I have", "show me my datapacks".
+- User says "which datapack am I on", "which datapack is active", "what's pinned".
+- User says "clear datapack", "unpin datapack", "stop using <name>".
+- The first Meko MCP write of a turn AND `memory_search` for `meko_active_datapack` returned no result AND the user has more than one datapack — proactively offer to pin one.
+
+## On every Meko-touching turn (not just when this skill triggers)
+
+Before issuing a Meko MCP write tool call (memory_add, db_run_write_query, conversation_add_message, etc.), if you don't already know the active pin from this turn's earlier work:
+
+```
+memory_search(scope="read",
+              query="meko_active_datapack",
+              agent_id="claude_desktop",
+              conversation_id="<this conversation's id>",
+              limit=1)
+```
+
+Parse the result. If a pin row is present, extract the UUID from the text body (after `meko_active_datapack=`) and pass it as `datapack_id` to every Meko MCP call this turn. If not, omit `datapack_id` and let the server resolve the default.
+
+This is once per turn, not once per call. Cache within the turn.
+
+## The flow
+
+### 1. List
+
+Use a **temporary** conversation for browsing only. Call
+`conversation_create(scope="write", agent_id="claude_desktop", title="Claude
+Desktop datapack selection")` and use its returned ID for the read-only
+`datapack_list` below and for the pin `memory_add`/`memory_update` in step 4.
+
+**Do not reuse this conversation for later capture.** It lives in whatever
+datapack was active when it was created (typically the default), and a
+conversation cannot move between datapacks. Once a datapack is pinned, capture
+must flow through a *new* conversation created in the selected datapack — see
+step 5.
+
+```
+datapack_list(scope="read", conversation_id="<this conversation's id>")
+```
+
+The response is an array; the fields you'll use are `datapack_id`,
+`datapack_name`, `created_at`, and `account_id`.
+
+If the response has zero entries, tell the user: *"You don't have any datapacks yet. Run `datapack_create(scope='admin', name='<name>')` to make one, or visit the Meko Cloud console."* Stop here.
+
+If the response has exactly **one** entry, **auto-select it**. Print: *"Only one datapack: `<name>`. Auto-selecting. Run `meko-select-datapack-desktop` again with `clear` to unset."* Skip the table; jump to step 4 (persist) and step 5 (confirm).
+
+### 2. Render the table
+
+For 2+ datapacks, render a numbered table. **Page size 10.** Default sort: `created_at DESC` (newest first).
+
+```
+Your datapacks (showing 1-10 of 14):
+
+#   Name                                   Role    Created       Status     Active?
+1   meko-local-setup                       Owner   2026-04-30    ready       ←  (pinned)
+2   meko_default_datapack                  Owner   2026-04-30    ready
+3   prod-research                          Owner   2026-04-12    ready
+…
+
+Reply with: a number (1-10) to pin · a substring to search · `next` / `prev` to page
+            · `clear` to unset · `cancel` to leave the current pin alone
+
+Note: Role is hardcoded to "Owner" today. Shared / Viewer / Contributor /
+Maintainer roles are pending upstream backend work — see references/role-display-future.md.
+```
+
+Mark the currently-pinned row with `←  (pinned)` based on the `memory_search` result (if any).
+
+### 3. Parse the user's reply
+
+- **Integer in range** → that row is the choice.
+- **Substring** → re-render filtered. If it narrows to one row, that's the choice.
+- **`next` / `prev`** → re-render next/previous page.
+- **`cancel`** → leave any existing pin in place; print *"Cancelled. Active datapack unchanged."* Stop.
+- **`clear` / `none` / `unpin`** → see step 4's clear path.
+- **Unrecognized** → re-prompt with the legend.
+
+### 4. Persist
+
+**On first pin (no existing pin memory):**
+
+```
+memory_add(scope="write",
+           text="meko_active_datapack=<uuid> name=<name> selected_at=<iso8601>",
+           agent_id="claude_desktop",
+           conversation_id="<this conversation's id>",
+           metadata='{"type":"active-datapack-pin"}')
+```
+
+Verify the write with `memory_search` (the standard Meko verify-after-write rule from `meko-mcp-tools-desktop`). Capture the returned memory `id`.
+
+**On switch (existing pin memory found):**
+
+```
+memory_update(scope="write",
+              memory_id="<existing pin id>",
+              text="meko_active_datapack=<new uuid> name=<new name> selected_at=<iso8601>",
+              agent_id="claude_desktop",
+              conversation_id="<this conversation's id>")
+```
+
+Always update — never `memory_add` a second pin. Two pin memories will produce ambiguous reads.
+
+**On clear:**
+
+```
+memory_delete_by_id(scope="write",
+                    memory_id="<existing pin id>",
+                    agent_id="claude_desktop",
+                    conversation_id="<this conversation's id>")
+```
+
+If `memory_search` returned no pin, there's nothing to delete — print *"No pin was set; nothing to clear."* and stop.
+
+**Conversation transition after a clear (same rule as a switch).** The pin memory is now gone, but the session's current conversation still physically lives in the datapack that was pinned when it was created — a conversation cannot move to the default. You must pick exactly one of these; do not mix them:
+
+- **Option A — keep capturing to the current conversation this session.** It stays in its original (now-unpinned) datapack, so you must keep passing that **same old `datapack_id`** on its `conversation_add_message` calls — do NOT switch it to the default (that would fail). The clear only affects *new* sessions. Disclose: *"Pin cleared. This chat keeps saving to `<old datapack name>`; new chats will use the default datapack."*
+- **Option B — start default-datapack capture immediately.** Create a **new** conversation with no `datapack_id` (`conversation_create(scope="write", agent_id="claude_desktop")`) and post all subsequent turns there. Stop posting to the old conversation. Disclose: *"Pin cleared. Started a new chat context saving to the default datapack."*
+
+Default to Option A (least disruptive) unless the user wants the switch to take effect right now. Either way, never send `datapack_id=default` to the pre-existing pinned conversation.
+
+### 5. Confirm
+
+```
+Pinned datapack `<name>` (`<uuid>`) for Claude Desktop.
+
+This is stored as a memory under agent_id="claude_desktop". It will persist
+across sessions until you run this skill again with `clear` (or `switch` to
+a different datapack).
+
+I'll read this pin via `memory_search` before each Meko MCP write so the
+right `datapack_id` flows through automatically.
+```
+
+**Then start a fresh conversation for capture in the selected datapack.** The
+temporary selection conversation from step 1 belongs to the datapack that was
+active when it was created and cannot be moved. For subsequent capture this
+session, call `conversation_create(scope="write", agent_id="claude_desktop",
+datapack_id="<the newly pinned uuid>", title="<topic>")` and post turns
+(`conversation_add_message`) to *that* conversation with the same
+`datapack_id`. Do not keep posting to the selection conversation — doing so
+would split capture across the old and new datapacks or fail outright.
+
+## Edge cases
+
+- **Multiple pin memories somehow exist** — the user (or a buggy earlier run) created duplicates. Use the most recent (highest `selected_at`); offer to delete the others.
+- **The pinned datapack no longer exists on the server** — the next Meko MCP call will fail with a not-found error. Re-run the skill to pick a new one or `clear` the stale pin.
+- **memory_search times out or fails** — fall back to the server default (omit `datapack_id`) and tell the user *"Couldn't read the active-datapack pin. Using server default for this call."* Don't guess a UUID.
+- **User explicitly overrides for a single call** — pass the user's `datapack_id` for that one call. Do NOT update the pin memory.
+
+## Critical: do NOT use other persistence mechanisms
+
+Don't write to local files, don't use environment variables, don't ask the user to paste the UUID into every prompt. A single tagged memory is the entire mechanism. Anything else creates drift between what you think is pinned and what `memory_search` will report.
+
+## Reference sections
+
+| File | What it covers |
+|------|---------------|
+| `references/cookbook.md` | Sample list / search / select / clear transcripts on Desktop |
+| `references/troubleshooting.md` | Pin not recalled, duplicate pins, stale UUID recovery |

package/assets/skills/meko-select-datapack-desktop/references/cookbook.md

@@ -0,0 +1,121 @@
+# Cookbook — meko-select-datapack-desktop
+
+Concrete transcripts of the four flows the skill supports on Claude Desktop.
+
+## Flow 1 — First pin (no existing pin memory)
+
+**User:** `pin prod-research as my active datapack`
+
+**Skill:**
+```
+> memory_search(query="meko_active_datapack", agent_id="claude_desktop", limit=1)
+[empty]
+
+> datapack_list(scope="read")
+[14 entries returned, filtering by "prod-research"]
+
+One match: `prod-research`. Pinning.
+
+> memory_add(scope="write",
+             text="meko_active_datapack=8b1c…f4a2 name=prod-research selected_at=2026-05-25T18:42:00Z",
+             agent_id="claude_desktop",
+             conversation_id="<conv-id>",
+             metadata='{"type":"active-datapack-pin"}')
+[returns id=mem_abc123]
+
+> memory_search(query="meko_active_datapack", agent_id="claude_desktop", limit=1)
+[verifies the row exists]
+
+Pinned datapack `prod-research` (`8b1c…f4a2`) for Claude Desktop.
+
+Stored as a memory under agent_id="claude_desktop"; persists across sessions
+until you run this skill again with `clear` or `switch`.
+
+I'll read this pin via memory_search before each Meko MCP write so the right
+datapack_id flows through automatically.
+```
+
+## Flow 2 — Switch (pin memory already exists)
+
+**User:** `switch to the q2-roadmap-deck datapack`
+
+**Skill:**
+```
+> memory_search(query="meko_active_datapack", agent_id="claude_desktop", limit=1)
+[returns id=mem_abc123, text="meko_active_datapack=8b1c…f4a2 name=prod-research …"]
+
+> datapack_list(scope="read")
+[14 entries returned, filtering by "q2-roadmap-deck"]
+
+One match: `q2-roadmap-deck`. Switching pin.
+
+> memory_update(scope="write",
+                memory_id="mem_abc123",
+                text="meko_active_datapack=4c2e…a991 name=q2-roadmap-deck selected_at=2026-05-25T19:05:00Z",
+                agent_id="claude_desktop",
+                conversation_id="<conv-id>")
+
+Switched pin from `prod-research` to `q2-roadmap-deck` (`4c2e…a991`).
+```
+
+The `memory_update` is critical here — using `memory_add` again would create a duplicate pin memory.
+
+## Flow 3 — Single-datapack auto-select
+
+**User:** (first Meko write attempt, no pin yet)
+
+**Skill:**
+```
+> memory_search(query="meko_active_datapack", agent_id="claude_desktop", limit=1)
+[empty]
+
+> datapack_list(scope="read")
+[1 entry returned]
+
+Only one datapack: `meko-local-setup`. Auto-selecting.
+
+> memory_add(scope="write",
+             text="meko_active_datapack=a17d…cc91 name=meko-local-setup selected_at=…",
+             agent_id="claude_desktop",
+             conversation_id="<conv-id>",
+             metadata='{"type":"active-datapack-pin"}')
+
+Pinned datapack `meko-local-setup` (`a17d…cc91`). Run this skill again with
+`clear` to unset.
+```
+
+## Flow 4 — Clear
+
+**User:** `unpin datapack`
+
+**Skill:**
+```
+> memory_search(query="meko_active_datapack", agent_id="claude_desktop", limit=1)
+[returns id=mem_abc123]
+
+> memory_delete_by_id(scope="write",
+                      memory_id="mem_abc123",
+                      agent_id="claude_desktop",
+                      conversation_id="<conv-id>")
+
+Pin cleared. Subsequent Meko MCP calls will use the server default.
+```
+
+If `memory_search` returned empty: *"No pin was set; nothing to clear."*
+
+## Flow 5 — Read-the-pin pattern (every Meko-touching turn)
+
+This isn't a user-triggered flow — it's the per-turn lookup the skill teaches you to do silently before any Meko MCP write:
+
+```
+> memory_search(query="meko_active_datapack", agent_id="claude_desktop",
+                conversation_id="<conv-id>", limit=1)
+[returns text="meko_active_datapack=8b1c…f4a2 name=prod-research …"]
+
+# Extract UUID after "meko_active_datapack=" → 8b1c…f4a2
+
+> memory_add(scope="write", text="…", datapack_id="8b1c…f4a2",
+             agent_id="claude_desktop", conversation_id="<conv-id>")
+```
+
+Cache the UUID for the rest of the turn — don't call `memory_search` once per Meko tool call.