@toolbeltai/skills 0.1.4 → 0.2.1

package/README.md

@@ -10,8 +10,8 @@ npx @toolbeltai/skills install
 ```
 
 Copies every skill to `~/.claude/skills/` (flat, per the AgentSkills spec).
-Restart Claude Code and you'll see them as slash commands: `/run-toolbelt`,
-`/geo-analyst`, …
+Restart Claude Code and you'll see them as slash commands: `/toolbelt-start`,
+`/toolbelt-geo`, …
 
 No account required; no network calls to Toolbelt. Skills work against any
 Toolbelt MCP server (cloud or self-hosted).
@@ -31,14 +31,13 @@ agent, and installs these skills — all at once.
 
 | Skill | Command | What it does |
 | --- | --- | --- |
-| [run-toolbelt](run-toolbelt/) | `/run-toolbelt` | Onboard, upload docs, connect data, ask questions |
-| [geo-analyst](geo-analyst/) | `/geo-analyst` | GPU-accelerated geospatial — queries and map rendering |
-| [knowledge-graph](knowledge-graph/) | `/knowledge-graph` | Auto-extract entities from docs, explore with Cypher |
-| [multi-agent-workspace](multi-agent-workspace/) | `/multi-agent-workspace` | Shareable MCP URL for multi-agent collaboration |
-| [sql-analyst](sql-analyst/) | `/sql-analyst` | Upload a CSV, ask plain English, get SQL + results |
-| [streaming-analyst](streaming-analyst/) | `/streaming-analyst` | Connect Kafka, aggregate, detect anomalies |
-| [vector-search](vector-search/) | `/vector-search` | Upload a document, retrieve semantically similar passages |
-| [data-blend](data-blend/) | `/data-blend` | Combine multiple tables with cross-table JOINs |
+| [toolbelt-start](toolbelt-start/) | `/toolbelt-start` | Onboard end-to-end — provision, ingest, first query |
+| [toolbelt-analyze](toolbelt-analyze/) | `/toolbelt-analyze` | Upload 1+ CSVs, ask in plain English, get SQL answers (single-table or multi-table JOIN) |
+| [toolbelt-find](toolbelt-find/) | `/toolbelt-find` | Upload a document, retrieve passages by semantic similarity |
+| [toolbelt-entities](toolbelt-entities/) | `/toolbelt-entities` | Auto-extract entities and relationships from docs, explore with Cypher |
+| [toolbelt-geo](toolbelt-geo/) | `/toolbelt-geo` | GPU-accelerated geospatial — distance, containment, routing, map rendering |
+| [toolbelt-stream](toolbelt-stream/) | `/toolbelt-stream` | Connect Kafka, aggregate over windows, detect anomalies |
+| [toolbelt-invite](toolbelt-invite/) | `/toolbelt-invite` | Emit a connection URL so another agent can join this workspace |
 
 ## Works with
 

package/assets/demos/{geo-analyst-demo.sh → toolbelt-geo-demo.sh}

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Simulates the geo-analyst skill running inside Claude Code
+# Simulates the toolbelt-geo skill running inside Claude Code
 
 G='\033[0;32m'   # green
 B='\033[0;34m'   # blue
@@ -10,7 +10,7 @@ W='\033[1;37m'   # bold white
 NC='\033[0m'
 
 printf "\n"
-printf "${D}> /geo-analyst${NC}\n"
+printf "${D}> /toolbelt-geo${NC}\n"
 sleep 0.8
 
 printf "\n"

package/assets/demos/{run-toolbelt-demo.sh → toolbelt-start-demo.sh}

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Simulates the run-toolbelt skill running inside Claude Code
+# Simulates the toolbelt-start skill running inside Claude Code
 
 G='\033[0;32m'   # green
 B='\033[0;34m'   # blue
@@ -10,7 +10,7 @@ W='\033[1;37m'   # bold white
 NC='\033[0m'
 
 printf "\n"
-printf "${D}> /run-toolbelt document_url=https://docs.toolbelt.ai/intro.pdf question=\"What is Toolbelt?\"${NC}\n"
+printf "${D}> /toolbelt-start document_url=https://docs.toolbelt.ai/intro.pdf question=\"What is Toolbelt?\"${NC}\n"
 sleep 0.8
 
 printf "\n"

package/bin/install.js

@@ -26,6 +26,21 @@ const PKG_ROOT = join(dirname(fileURLToPath(import.meta.url)), '..');
 const TARGET = join(homedir(), '.claude', 'skills');
 const LEGACY_NESTED_DIR = join(TARGET, 'toolbelt');
 
+// Pre-0.2.0 skill folder names. Removed on install so upgraders don't
+// see ghost slash commands for skills that were renamed or merged.
+// Added 2026-04-23 with the toolbelt-* prefix rename; safe to drop this
+// list in a future major once the userbase has cycled.
+const LEGACY_SKILL_NAMES = [
+  'run-toolbelt',
+  'sql-analyst',
+  'data-blend',
+  'vector-search',
+  'knowledge-graph',
+  'geo-analyst',
+  'streaming-analyst',
+  'multi-agent-workspace',
+];
+
 /** Any top-level directory containing a SKILL.md is a skill. */
 function listSkills() {
   return readdirSync(PKG_ROOT, { withFileTypes: true })
@@ -39,6 +54,13 @@ function cleanupLegacy() {
     rmSync(LEGACY_NESTED_DIR, { recursive: true, force: true });
     console.log(`  migrated: removed legacy ~/.claude/skills/toolbelt/`);
   }
+  for (const name of LEGACY_SKILL_NAMES) {
+    const p = join(TARGET, name);
+    if (existsSync(p)) {
+      rmSync(p, { recursive: true, force: true });
+      console.log(`  migrated: removed legacy skill ${name}/`);
+    }
+  }
 }
 
 function cmdInstall() {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@toolbeltai/skills",
-  "version": "0.1.4",
-  "description": "Official Toolbelt skills for Claude Code and MCP agents — run-toolbelt, geo-analyst, knowledge-graph, sql-analyst, vector-search, streaming-analyst, multi-agent-workspace, data-blend.",
+  "version": "0.2.1",
+  "description": "Official Toolbelt skills — named /toolbelt-* flows (start, analyze, find, entities, geo, stream, invite) that teach any MCP-capable agent to orchestrate Toolbelt's MCP tools end-to-end.",
   "license": "MIT",
   "homepage": "https://toolbelt.ai",
   "repository": {
@@ -14,14 +14,17 @@
   "author": "Toolbelt",
   "keywords": [
     "toolbelt",
-    "claude-code",
     "mcp",
-    "skills",
+    "agent-skills",
+    "claude-code",
     "openclaw",
+    "cursor",
+    "windsurf",
     "sql",
+    "rag",
     "knowledge-graph",
     "geospatial",
-    "vector-search"
+    "streaming"
   ],
   "bin": {
     "toolbelt-skills": "./bin/install.js"
@@ -29,14 +32,13 @@
   "files": [
     "bin",
     "assets",
-    "data-blend",
-    "geo-analyst",
-    "knowledge-graph",
-    "multi-agent-workspace",
-    "run-toolbelt",
-    "sql-analyst",
-    "streaming-analyst",
-    "vector-search",
+    "toolbelt-start",
+    "toolbelt-analyze",
+    "toolbelt-find",
+    "toolbelt-entities",
+    "toolbelt-geo",
+    "toolbelt-stream",
+    "toolbelt-invite",
     "LICENSE",
     "README.md"
   ],

package/toolbelt-analyze/SKILL.md

@@ -0,0 +1,307 @@
+---
+name: toolbelt-analyze
+description: >
+  Upload one or more CSV tables and answer natural-language questions by
+  generating and executing SQL. Handles single-table analytics (totals,
+  averages, group-by, filtering) AND multi-table JOINs across related
+  datasets (orders + customers, sensors + metadata, events + dimensions).
+  Use when an agent has structured rows/columns — one table or several
+  that share a key — and needs analytical answers: trends, breakdowns,
+  comparisons, rankings, correlations. NOT for unstructured documents
+  (use toolbelt-find or toolbelt-entities), lat/lon or WKT data (use
+  toolbelt-geo), or live streams (use toolbelt-stream).
+license: MIT
+compatibility: >
+  Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
+  MCP-compatible AI agent (Claude Code, Claude Desktop, OpenClaw, or any client
+  that supports MCP server connections). MCP connection must be pre-established
+  before invocation.
+metadata:
+  author: toolbeltai
+  version: "2.0"
+  homepage: "https://toolbelt.ai/docs/sql"
+---
+
+Upload one or more CSV tables and answer natural-language questions about
+them using Toolbelt MCP tools. Handles both single-table queries and
+multi-table JOINs on related datasets — pick the right approach based on
+the uploaded data and the question. Work through each phase in order
+without prompting for user input. On unrecoverable error, emit a
+structured failure and halt.
+
+## When Not To Use
+
+- For unstructured text or documents — use `toolbelt-find` (retrieval) or `toolbelt-entities` (entity/relationship extraction).
+- For real-time or streaming data — use `toolbelt-stream`.
+- For spatial data with lat/lon coordinates — use `toolbelt-geo`.
+
+## Invocation Parameters
+
+Extract these from the args string or conversation context before starting:
+
+| Parameter | Required | Description |
+|---|---|---|
+| `namespace_id` | No | UUID of target namespace. Auto-select if omitted and only one exists; fail if ambiguous. |
+| `csv_inputs` | No | Array of `{ name, content }` objects for multi-table analysis (e.g. orders + customers). Preferred when two or more related CSVs need JOINs. |
+| `csv_content` | No | Single CSV text (shorthand for `csv_inputs: [{ name: asset_name, content: ... }]`). |
+| `asset_name` | No | Name for the single uploaded table (when `csv_content` is used). Defaults to `sales-data`. |
+| `question` | No | Natural language question. Defaults vary by input shape (see below). |
+
+If neither `csv_inputs` nor `csv_content` is provided, use the single built-in
+sample dataset below with `asset_name = "sales-data"`.
+
+The resolved list of uploads is called **`uploads`** for the rest of this
+skill — each element has `{ name, content }`.
+
+---
+
+## Default Sample Data
+
+If no inputs are provided, use this single sales dataset verbatim as
+`uploads = [{ name: "sales-data", content: <csv below> }]`:
+
+```
+order_id,date,region,product,category,quantity,unit_price,amount,rep
+1001,2024-01-05,Northeast,Widget Pro,Hardware,12,49.99,599.88,Alice Chen
+1002,2024-01-08,Southeast,Gadget Basic,Software,5,29.99,149.95,Bob Martinez
+1003,2024-01-12,Midwest,Widget Pro,Hardware,8,49.99,399.92,Carol Singh
+1004,2024-01-15,West,Service Plan,Services,3,199.00,597.00,David Park
+1005,2024-01-19,Northeast,Gadget Basic,Software,20,29.99,599.80,Alice Chen
+1006,2024-01-22,West,Widget Pro,Hardware,6,49.99,299.94,Emma Lopez
+1007,2024-02-03,Southeast,Service Plan,Services,2,199.00,398.00,Bob Martinez
+1008,2024-02-07,Midwest,Gadget Plus,Software,15,79.99,1199.85,Frank Kim
+1009,2024-02-11,Northeast,Widget Pro,Hardware,10,49.99,499.90,Alice Chen
+1010,2024-02-14,West,Gadget Basic,Software,8,29.99,239.92,David Park
+1011,2024-02-18,Southeast,Gadget Plus,Software,4,79.99,319.96,Carol Singh
+1012,2024-02-21,Midwest,Service Plan,Services,1,199.00,199.00,Frank Kim
+1013,2024-03-02,Northeast,Service Plan,Services,5,199.00,995.00,Alice Chen
+1014,2024-03-06,West,Gadget Plus,Software,9,79.99,719.91,Emma Lopez
+1015,2024-03-10,Southeast,Widget Pro,Hardware,7,49.99,349.93,Bob Martinez
+1016,2024-03-14,Midwest,Gadget Basic,Software,11,29.99,329.89,Carol Singh
+1017,2024-03-18,Northeast,Gadget Plus,Software,6,79.99,479.94,David Park
+1018,2024-03-22,West,Service Plan,Services,4,199.00,796.00,Emma Lopez
+1019,2024-03-25,Southeast,Widget Pro,Hardware,3,49.99,149.97,Frank Kim
+1020,2024-03-28,Midwest,Widget Pro,Hardware,14,49.99,699.86,Carol Singh
+```
+
+Default `question` for the single-table case:
+`What is the total sales amount by region?`
+
+For multi-table cases (`csv_inputs.length >= 2`) with no `question` provided,
+ask the user to clarify — don't guess a default cross-table question.
+
+---
+
+## Phase 0: Verify Connection
+
+Call `toolbelt_list_namespaces` (no arguments) immediately.
+
+- **If it succeeds:** proceed to Phase 1 using the returned namespaces.
+- **If it fails:** emit structured failure and halt.
+
+```
+FAILURE: Toolbelt MCP connection is not established.
+The MCP server must be connected before invoking this skill.
+See: https://toolbelt.ai/docs/mcp for setup instructions.
+```
+
+---
+
+## Phase 1: Resolve Namespace
+
+Use the namespaces returned from Phase 0.
+
+Resolution order:
+1. If `namespace_id` was provided as a parameter, use it directly.
+2. If only one namespace exists, use it.
+3. If multiple exist and no `namespace_id` was specified, emit structured failure and halt.
+
+```
+FAILURE: Multiple namespaces found and none specified.
+Available: [<list namespace display names and IDs>]
+Re-invoke with namespace_id=<uuid>.
+```
+
+Store the resolved `namespace_id` — pass it to every subsequent tool call.
+
+---
+
+## Phase 2: Upload Each CSV
+
+Resolve `uploads` per the Invocation Parameters section.
+
+**For each** `{ name, content }` in `uploads`, call `toolbelt_save`:
+
+```json
+{
+  "asset_type": "document",
+  "namespace_id": "<namespace_id>",
+  "name": "<name>",
+  "file_name": "<name>.csv",
+  "content": "<content>",
+  "content_encoding": "text",
+  "data_format": "csv"
+}
+```
+
+Collect the returned `asset_id` for each upload into an array `asset_ids`.
+Track the upload count as `upload_count`.
+
+If any `toolbelt_save` fails, emit structured failure naming which upload
+failed and halt — partial multi-table ingests can't be joined.
+
+---
+
+## Phase 3: Poll for All Ingestions
+
+Call `toolbelt_jobs` with `{ "namespace_id": "<namespace_id>" }` every 10 seconds.
+
+Wait until **every** `ingest` job for the `asset_ids` from Phase 2 reaches `completed`.
+
+Typical duration: 15–60 seconds per file. Maximum wait: 3 minutes total.
+
+If any job reaches `failed` or the timeout elapses, emit structured failure:
+```
+FAILURE: Ingestion did not complete for <asset_name>.
+Job status: <last observed status>
+Completed so far: <N of M>
+```
+
+---
+
+## Phase 4: Get Schema Context
+
+Call `toolbelt_context` with `{ "namespace_id": "<namespace_id>" }`.
+
+For each uploaded `asset_name` (from Phase 2), locate the corresponding
+table in the returned context and record:
+- `table_name`: the SQL table name
+- `column_names`: columns in that table
+- `row_count`: row count if provided
+
+Store all of them in a `tables` array so Phase 5 can reason about JOINs.
+
+---
+
+## Phase 5: Answer the Question
+
+Resolve `question` per the Invocation Parameters section.
+
+**Decide on approach using `upload_count`:**
+
+### If `upload_count == 1` (single-table analytics)
+
+Prefer `toolbelt_search` (it routes through our hybrid + NL→SQL layer):
+
+```json
+{
+  "question": "<question>",
+  "namespace_id": "<namespace_id>",
+  "synthesize": true
+}
+```
+
+If `toolbelt_search` does not return SQL, fall back to `toolbelt_sql`
+with a query you write from the single table's schema:
+
+```json
+{
+  "namespace_id": "<namespace_id>",
+  "query": "SELECT <...> FROM <table_name> ..."
+}
+```
+
+### If `upload_count >= 2` (multi-table JOIN)
+
+1. From the `tables` array collected in Phase 4, **identify candidate join
+   keys** — columns that appear in two or more tables with compatible types
+   and matching name patterns (e.g. `customer_id` in `orders` + `customers`).
+2. Write a `SELECT` that JOINs on the identified key(s) and answers the
+   user's question. Prefer explicit `JOIN ... ON ...` (never implicit join).
+3. Call `toolbelt_sql` directly with the JOIN query:
+
+```json
+{
+  "namespace_id": "<namespace_id>",
+  "query": "SELECT a.<col>, SUM(b.<col>) FROM <t1> a JOIN <t2> b ON a.<key> = b.<key> GROUP BY a.<col>"
+}
+```
+
+If no join key is identifiable, emit structured failure explaining which
+tables were uploaded and asking the caller to supply a join key:
+```
+FAILURE: Uploaded tables have no obvious join key.
+Tables and columns: [<summary>]
+Re-invoke with a question that specifies which column(s) relate the tables.
+```
+
+### For either case, parse the result:
+
+- `answer`: synthesized natural-language answer (if using `toolbelt_search`) or a one-sentence summary you compose from the rows (if using `toolbelt_sql` directly)
+- `sql_generated`: the SQL that ran
+- `row_count`: rows returned
+- `sources`: cited tables/assets
+
+Record the path used as `query_method` — `"search"` (NL→SQL via hybrid),
+`"direct_sql_single"` (one-table direct), or `"direct_sql_join"` (multi-table JOIN).
+
+---
+
+## Phase 6: Structured Output
+
+After all phases complete, emit a single structured result:
+
+```
+RESULT:
+  namespace_id: <uuid>
+  uploaded_tables:
+    - asset_name: <name>
+      table_name: <sql table name>
+      column_names: [<list>]
+      row_count_ingested: <rows>
+  upload_count: <N>
+  phases_run: [0, 1, 2, 3, 4, 5]
+
+  question: "<question asked>"
+  query_method: "<search | direct_sql_single | direct_sql_join>"
+  sql_generated: |
+    <SQL query executed>
+  row_count: <rows returned>
+  answer: |
+    <natural-language answer>
+  sources: [<tables cited>]
+```
+
+---
+
+## Tool Reference
+
+| Phase | Tool(s) |
+|---|---|
+| 0. Verify connection | `toolbelt_list_namespaces` |
+| 1. Resolve namespace | (from Phase 0 result) |
+| 2. Upload each CSV | `toolbelt_save` (once per input) |
+| 3. Poll for ingestion | `toolbelt_jobs` |
+| 4. Get schema context | `toolbelt_context` |
+| 5. Answer | `toolbelt_search` (single-table NL path), `toolbelt_sql` (direct; required for JOINs) |
+| 6. Emit result | (structured output) |
+
+---
+
+## Multi-Table Example
+
+Invocation:
+```
+/toolbelt-analyze csv_inputs=[
+  { name: "orders",    content: "order_id,customer_id,amount,..." },
+  { name: "customers", content: "customer_id,region,tier,..." }
+] question="Total amount by customer region"
+```
+
+Expected phases:
+- Phase 2: `toolbelt_save` for `orders`, then `toolbelt_save` for `customers`
+- Phase 3: poll both `ingest` jobs to completion
+- Phase 4: context returns two tables; record both schemas
+- Phase 5: identify `customer_id` as the join key, run
+  `SELECT c.region, SUM(o.amount) FROM orders o JOIN customers c ON o.customer_id = c.customer_id GROUP BY c.region`
+- Phase 6: structured result with `query_method = "direct_sql_join"` and both tables in `uploaded_tables`

package/{knowledge-graph → toolbelt-entities}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: knowledge-graph
+name: toolbelt-entities
 description: >
   Upload a document; Toolbelt automatically extracts entities (people, orgs,
   places, concepts) and their relationships into a knowledge graph — no schema
@@ -7,7 +7,7 @@ description: >
   trace connections. Use when an agent needs to map who-relates-to-whom, surface
   hidden links across documents, answer multi-hop relationship questions, or
   identify central entities in a corpus. NOT for flat semantic passage retrieval
-  (use vector-search) or tabular analytics (use sql-analyst).
+  (use toolbelt-find) or tabular analytics (use toolbelt-analyze).
 license: MIT
 compatibility: >
   Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
@@ -17,7 +17,7 @@ compatibility: >
 metadata:
   author: toolbeltai
   version: "1.0"
-  homepage: "https://toolbelt.ai/docs/knowledge-graph"
+  homepage: "https://toolbelt.ai/docs/toolbelt-entities"
 ---
 
 Extract a knowledge graph from a document and explore it autonomously using
@@ -26,8 +26,8 @@ user input. On unrecoverable error, emit a structured failure and halt.
 
 ## When Not To Use
 
-- For structured tabular data (CSV, SQL tables) — use `sql-analyst` instead.
-- When entity and relationship extraction is not needed — use `sql-analyst` or `streaming-analyst` for the appropriate data type.
+- For structured tabular data (CSV, SQL tables) — use `toolbelt-analyze` instead.
+- When entity and relationship extraction is not needed — use `toolbelt-analyze` or `toolbelt-stream` for the appropriate data type.
 
 ## Invocation Parameters
 

package/{vector-search → toolbelt-find}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: vector-search
+name: toolbelt-find
 description: >
   Upload a document and retrieve passages by semantic similarity to a
   natural-language query. Ranks content by meaning, not keyword overlap. Use
   when an agent needs to ground answers in source documents (RAG), find related
   content, retrieve passages by concept, or answer "what does this doc say
   about X" where X isn't a verbatim phrase. NOT for exact keyword/regex search,
-  structured table queries (use sql-analyst), or entity-relationship extraction
-  (use knowledge-graph).
+  structured table queries (use toolbelt-analyze), or entity-relationship extraction
+  (use toolbelt-entities).
 license: MIT
 compatibility: >
   Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
@@ -26,10 +26,10 @@ unrecoverable error, emit a structured failure and halt.
 
 ## When Not To Use
 
-- For structured tabular data (CSV, SQL tables) — use `sql-analyst` instead.
-- For aggregate queries, counts, or filtering by exact values — use `sql-analyst`; vector search ranks by meaning, not criteria.
-- For entity and relationship extraction — use `knowledge-graph` instead.
-- When you need a synthesized answer that may draw on SQL tables — use `sql-analyst` with `toolbelt_search` (hybrid routing) instead.
+- For structured tabular data (CSV, SQL tables) — use `toolbelt-analyze` instead.
+- For aggregate queries, counts, or filtering by exact values — use `toolbelt-analyze`; vector search ranks by meaning, not criteria.
+- For entity and relationship extraction — use `toolbelt-entities` instead.
+- When you need a synthesized answer that may draw on SQL tables — use `toolbelt-analyze` with `toolbelt_search` (hybrid routing) instead.
 
 ## How This Differs From `toolbelt_search`
 
@@ -46,7 +46,7 @@ Extract these from the args string or conversation context before starting:
 |---|---|---|
 | `namespace_id` | No | UUID of target namespace. Auto-select if omitted and only one exists; fail if ambiguous. |
 | `document_content` | No | Raw text to upload. Uses the embedded sample document if omitted. |
-| `document_name` | No | Name for the document asset. Defaults to `vector-search-sample`. |
+| `document_name` | No | Name for the document asset. Defaults to `toolbelt-find-sample`. |
 | `question` | No | Natural language query to search for. Defaults to `What are the effects on coastal ecosystems?` |
 | `skip_upload` | No | Set to `true` to skip Phases 2–3 and search existing namespace content. |
 
@@ -142,7 +142,7 @@ Store the resolved `namespace_id` — pass it to every subsequent tool call.
 Skip this phase if `skip_upload` is `true`.
 
 Resolve `document_content` (use parameter value or default sample above).
-Resolve `document_name` (use parameter value or default `vector-search-sample`).
+Resolve `document_name` (use parameter value or default `toolbelt-find-sample`).
 
 Call `toolbelt_save`:
 

package/{geo-analyst → toolbelt-geo}/README.md

@@ -1,7 +1,7 @@
-# geo-analyst
+# toolbelt-geo
 
-![geo-analyst demo](../assets/geo-analyst-demo.gif)
+![toolbelt-geo demo](../assets/toolbelt-geo-demo.gif)
 
 GPU-accelerated geospatial analytics agent powered by Toolbelt MCP. Uploads lat/lon sensor data, runs geospatial SQL queries (distance, point-in-polygon, track creation), and emits structured results.
 
-Invoke via `/geo-analyst` in Claude Code, or via the `Skill` tool in any MCP-capable agent.
+Invoke via `/toolbelt-geo` in Claude Code, or via the `Skill` tool in any MCP-capable agent.

package/{geo-analyst → toolbelt-geo}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: geo-analyst
+name: toolbelt-geo
 description: >
   GPU-accelerated geospatial analytics on Toolbelt — distance, point-in-polygon
   containment, nearest-neighbor, track creation, spatial joins. Upload lat/lon
   sensor readings or WKT geometries, then run spatial SQL queries. Use when an
   agent needs to answer geographic questions — how close is X to Y, which points
   fall inside a region, along which route, coverage overlap, or movement tracks
-  from raw GPS. NOT for non-spatial tabular analysis (use sql-analyst) or
-  document content (use vector-search).
+  from raw GPS. NOT for non-spatial tabular analysis (use toolbelt-analyze) or
+  document content (use toolbelt-find).
 license: MIT
 compatibility: >
   Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
@@ -27,8 +27,8 @@ without confirmation. On unrecoverable error, emit a structured failure and halt
 
 ## When Not To Use
 
-- For tabular data without lat/lon coordinates — use `sql-analyst` instead.
-- For unstructured text or documents — use `knowledge-graph` instead.
+- For tabular data without lat/lon coordinates — use `toolbelt-analyze` instead.
+- For unstructured text or documents — use `toolbelt-entities` instead.
 
 ## Invocation Parameters
 

package/{multi-agent-workspace → toolbelt-invite}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: multi-agent-workspace
+name: toolbelt-invite
 description: >
   Set up a Toolbelt namespace that multiple agents can share. Uploads a document,
   then emits a connection URL another agent can use to join the same workspace
   without re-ingesting. Use when handing off context between agents or sessions,
   when two agents need to collaborate on the same dataset, or when pre-staging
   data for a downstream agent. NOT needed for single-agent workflows — use
-  run-toolbelt instead.
+  toolbelt-start instead.
 license: MIT
 compatibility: >
   Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
@@ -26,7 +26,7 @@ prompting for user input. On unrecoverable error, emit a structured failure and
 ## When Not To Use
 
 - For single-agent workflows where data sharing between agents is not needed.
-- When you only need to analyze data yourself — use `sql-analyst`, `streaming-analyst`, or `knowledge-graph` instead.
+- When you only need to analyze data yourself — use `toolbelt-analyze`, `toolbelt-stream`, or `toolbelt-entities` instead.
 
 ## Invocation Parameters
 

package/{run-toolbelt → toolbelt-start}/README.md

@@ -1,10 +1,10 @@
-# run-toolbelt
+# toolbelt-start
 
-![run-toolbelt demo](../assets/run-toolbelt-demo.gif)
+![toolbelt-start demo](../assets/toolbelt-start-demo.gif)
 
 Autonomous end-to-end Toolbelt agent. Provisions a namespace, ingests documents, connects streaming data sources, and answers questions — all without human interaction.
 
-Invoke via `/run-toolbelt` in Claude Code, or via the `Skill` tool in any MCP-capable agent.
+Invoke via `/toolbelt-start` in Claude Code, or via the `Skill` tool in any MCP-capable agent.
 
 ---
 
@@ -31,7 +31,7 @@ Invoke via `/run-toolbelt` in Claude Code, or via the `Skill` tool in any MCP-ca
 ### Smoke test — connection and namespace only
 
 ```
-/run-toolbelt
+/toolbelt-start
 ```
 
 Runs phases 0–2. Verifies the MCP connection is live and resolves your namespace. No data is written.
@@ -41,11 +41,11 @@ Runs phases 0–2. Verifies the MCP connection is live and resolves your namespa
 ### Ingest a document and ask a question
 
 ```
-/run-toolbelt document_url=https://example.com/report.pdf question="What are the key findings?"
+/toolbelt-start document_url=https://example.com/report.pdf question="What are the key findings?"
 ```
 
 ```
-/run-toolbelt document_content="Q1 revenue was $4.2M across three product lines." document_name="q1-summary" question="What was Q1 revenue?"
+/toolbelt-start document_content="Q1 revenue was $4.2M across three product lines." document_name="q1-summary" question="What was Q1 revenue?"
 ```
 
 ---
@@ -53,7 +53,7 @@ Runs phases 0–2. Verifies the MCP connection is live and resolves your namespa
 ### Target a specific namespace
 
 ```
-/run-toolbelt namespace_id=<uuid> document_url=https://example.com/report.pdf question="Summarize this."
+/toolbelt-start namespace_id=<uuid> document_url=https://example.com/report.pdf question="Summarize this."
 ```
 
 Required when your account has multiple namespaces. Omit to auto-select when only one exists.
@@ -63,7 +63,7 @@ Required when your account has multiple namespaces. Omit to auto-select when onl
 ### Connect a Kafka source
 
 ```
-/run-toolbelt kafka_broker=kafka-broker:9092 kafka_topic=events kafka_schema="id INTEGER, event VARCHAR(256), ts TIMESTAMP"
+/toolbelt-start kafka_broker=kafka-broker:9092 kafka_topic=events kafka_schema="id INTEGER, event VARCHAR(256), ts TIMESTAMP"
 ```
 
 Connects the topic and verifies it is queryable. Combine with `question` to search over streaming data.
@@ -73,7 +73,7 @@ Connects the topic and verifies it is queryable. Combine with `question` to sear
 ### Full pipeline
 
 ```
-/run-toolbelt \
+/toolbelt-start \
   namespace_id=<uuid> \
   document_url=https://example.com/report.pdf \
   kafka_broker=kafka-broker:9092 \
@@ -89,7 +89,7 @@ Runs all phases: document ingestion, Kafka connection, and cross-source search.
 ### From another agent (Skill tool)
 
 ```javascript
-{ skill: "run-toolbelt", args: "namespace_id=<uuid> document_url=https://... question=..." }
+{ skill: "toolbelt-start", args: "namespace_id=<uuid> document_url=https://... question=..." }
 ```
 
 The skill emits a structured `RESULT:` block — parseable by the calling agent without human interpretation.

package/{run-toolbelt → toolbelt-start}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: run-toolbelt
+name: toolbelt-start
 description: >
   Provision a Toolbelt namespace, ingest a document or Kafka stream, and answer
   a question end-to-end — autonomously, without human steps. Use when an agent
   needs to set up a fresh Toolbelt workspace, add assets from scratch, connect a
   streaming source, or run a complete ingest→query pipeline. NOT for querying
-  data that is already ingested — use sql-analyst, vector-search, or
-  knowledge-graph for that.
+  data that is already ingested — use toolbelt-analyze, toolbelt-find, or
+  toolbelt-entities for that.
 license: MIT
 compatibility: >
   Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
@@ -27,8 +27,8 @@ without confirmation. On unrecoverable error, emit a structured failure and halt
 ## When Not To Use
 
 - When the Toolbelt MCP connection is not yet established — the connection must exist before invocation.
-- When you only need to query data already in Toolbelt — use `sql-analyst` instead.
-- When you only need to upload and analyze a CSV — use `sql-analyst` instead.
+- When you only need to query data already in Toolbelt — use `toolbelt-analyze` instead.
+- When you only need to upload and analyze a CSV — use `toolbelt-analyze` instead.
 
 ## Invocation Parameters
 

package/{streaming-analyst → toolbelt-stream}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: streaming-analyst
+name: toolbelt-stream
 description: >
   Connect a live Kafka topic (or use built-in simulated data) and run windowed
   aggregations plus standard-deviation anomaly detection on the stream. Use when
   an agent needs to analyze real-time or time-series data — IoT sensor readings,
   event logs, security events, fleet telemetry, transaction feeds — and answer
   questions about rates, trends, and outliers over time windows. NOT for static
-  tabular files (use sql-analyst) or document content (use vector-search).
+  tabular files (use toolbelt-analyze) or document content (use toolbelt-find).
 license: MIT
 compatibility: >
   Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
@@ -27,7 +27,7 @@ failure and halt.
 
 ## When Not To Use
 
-- For static batch tabular data — use `sql-analyst` instead.
+- For static batch tabular data — use `toolbelt-analyze` instead.
 - When real-time monitoring, windowed aggregation, or anomaly detection is not the goal.
 
 ## Invocation Parameters

package/data-blend/SKILL.md

@@ -1,280 +0,0 @@
----
-name: data-blend
-description: >
-  Upload two or more CSV tables into one Toolbelt namespace and run cross-table
-  JOIN queries to correlate them. Use when an agent has related datasets that
-  need to be combined — orders + customers, sensors + metadata, events +
-  dimensions, transactions + accounts — and questions span multiple tables that
-  share a key. NOT for single-table analysis (use sql-analyst), unstructured
-  text (use knowledge-graph), or entity-level relationship mapping across free
-  text (use knowledge-graph).
-license: MIT
-compatibility: >
-  Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
-  MCP-compatible AI agent (Claude Code, Claude Desktop, OpenClaw, or any client
-  that supports MCP server connections). MCP connection must be pre-established
-  before invocation.
-metadata:
-  author: toolbeltai
-  version: "1.0"
-  homepage: "https://toolbelt.ai/docs/sql"
----
-
-Upload multiple tables and run cross-table JOIN queries using Toolbelt MCP tools.
-Work through each phase in order without prompting for user input. On
-unrecoverable error, emit a structured failure and halt.
-
-## When Not To Use
-
-- For a single table — use `sql-analyst` instead.
-- For unstructured text or documents — use `knowledge-graph` instead.
-- For streaming/real-time data — use `streaming-analyst` instead.
-- For spatial data with lat/lon — use `geo-analyst` instead.
-
-## Invocation Parameters
-
-Extract these from the args string or conversation context before starting:
-
-| Parameter | Required | Description |
-|---|---|---|
-| `namespace_id` | No | UUID of target namespace. Auto-select if omitted and only one exists; fail if ambiguous. |
-| `table_a_content` | No | Raw CSV for the first table. Uses default `orders` sample if omitted. |
-| `table_a_name` | No | Asset name for the first table. Defaults to `orders`. |
-| `table_b_content` | No | Raw CSV for the second table. Uses default `customers` sample if omitted. |
-| `table_b_name` | No | Asset name for the second table. Defaults to `customers`. |
-| `join_query` | No | Custom SQL JOIN to execute in Phase 5. Uses default query if omitted. |
-| `skip_upload` | No | Set to `true` to skip Phases 2–4 and query tables already in the namespace. |
-
----
-
-## Default Sample Data
-
-If no `table_a_content` is provided, use this orders dataset verbatim:
-
-```
-order_id,customer_id,product,category,quantity,amount,order_date
-1001,C001,Widget Pro,Hardware,12,599.88,2024-01-05
-1002,C003,Gadget Basic,Software,5,149.95,2024-01-08
-1003,C002,Widget Pro,Hardware,8,399.92,2024-01-12
-1004,C004,Service Plan,Services,3,597.00,2024-01-15
-1005,C001,Gadget Basic,Software,20,599.80,2024-01-19
-1006,C005,Widget Pro,Hardware,6,299.94,2024-01-22
-1007,C003,Service Plan,Services,2,398.00,2024-02-03
-1008,C002,Gadget Plus,Software,15,1199.85,2024-02-07
-1009,C001,Widget Pro,Hardware,10,499.90,2024-02-11
-1010,C004,Gadget Basic,Software,8,239.92,2024-02-14
-1011,C005,Gadget Plus,Software,4,319.96,2024-02-18
-1012,C002,Service Plan,Services,1,199.00,2024-02-21
-1013,C001,Service Plan,Services,5,995.00,2024-03-02
-1014,C005,Gadget Plus,Software,9,719.91,2024-03-06
-1015,C003,Widget Pro,Hardware,7,349.93,2024-03-10
-1016,C002,Gadget Basic,Software,11,329.89,2024-03-14
-1017,C004,Gadget Plus,Software,6,479.94,2024-03-18
-1018,C005,Service Plan,Services,4,796.00,2024-03-22
-1019,C003,Widget Pro,Hardware,3,149.97,2024-03-25
-1020,C002,Widget Pro,Hardware,14,699.86,2024-03-28
-```
-
-If no `table_b_content` is provided, use this customers dataset verbatim:
-
-```
-customer_id,name,region,segment,account_manager
-C001,Meridian Corp,Northeast,Enterprise,Alice Chen
-C002,Delta Systems,Midwest,Enterprise,Carol Singh
-C003,Apex Solutions,Southeast,Mid-Market,Bob Martinez
-C004,Crest Industries,West,Mid-Market,David Park
-C005,Solaris Group,West,SMB,Emma Lopez
-```
-
-Default `join_query`:
-```sql
-SELECT
-  c.segment,
-  c.region,
-  COUNT(o.order_id) AS order_count,
-  ROUND(SUM(o.amount), 2) AS total_amount,
-  ROUND(AVG(o.amount), 2) AS avg_order_value
-FROM <orders_table> o
-JOIN <customers_table> c ON o.customer_id = c.customer_id
-GROUP BY c.segment, c.region
-ORDER BY total_amount DESC
-```
-
----
-
-## Phase 0: Verify Connection
-
-Call `toolbelt_list_namespaces` (no arguments) immediately.
-
-- **If it succeeds:** proceed to Phase 1 using the returned namespaces.
-- **If it fails:** emit structured failure and halt.
-
-```
-FAILURE: Toolbelt MCP connection is not established.
-The MCP server must be connected before invoking this skill.
-See: https://toolbelt.ai/docs/mcp for setup instructions.
-```
-
----
-
-## Phase 1: Resolve Namespace
-
-Use the namespaces returned from Phase 0.
-
-Resolution order:
-1. If `namespace_id` was provided as a parameter, use it directly.
-2. If only one namespace exists, use it.
-3. If multiple exist and no `namespace_id` was specified, emit structured failure and halt.
-
-```
-FAILURE: Multiple namespaces found and none specified.
-Available: [<list namespace display names and IDs>]
-Re-invoke with namespace_id=<uuid>.
-```
-
-Store the resolved `namespace_id` — pass it to every subsequent tool call.
-
----
-
-## Phase 2: Inspect Existing Tables
-
-Skip this phase if `skip_upload` is `true` — go directly to Phase 5.
-
-Call `toolbelt_context` with `{ "namespace_id": "<namespace_id>" }`.
-
-Check whether tables matching `table_a_name` and `table_b_name` already exist:
-- If both exist: skip Phases 3–4 and proceed to Phase 5 using their existing table names.
-- If one or both are missing: upload the missing ones in Phase 3.
-
-Store all resolved table names for use in Phase 5.
-
----
-
-## Phase 3: Upload Missing Tables
-
-For each table that does not already exist, call `toolbelt_save`:
-
-```json
-{
-  "asset_type": "document",
-  "namespace_id": "<namespace_id>",
-  "name": "<table_a_name or table_b_name>",
-  "file_name": "<name>.csv",
-  "content": "<csv_content>",
-  "content_encoding": "text",
-  "data_format": "csv"
-}
-```
-
-Record each returned `asset_id`.
-
----
-
-## Phase 4: Poll for Ingestion
-
-Call `toolbelt_jobs` with `{ "namespace_id": "<namespace_id>" }` every 10 seconds.
-
-Wait for the `ingest` job for each uploaded asset to reach `completed`. Typical duration: 15–60 seconds per table. Maximum wait: 3 minutes.
-
-If any job reaches `failed` or the timeout elapses, emit structured failure and halt:
-```
-FAILURE: Table ingestion did not complete.
-Asset: <table name>
-Job status: <last observed status>
-```
-
-After all jobs complete, call `toolbelt_context` to retrieve the final SQL table names for all assets. Store as `table_a` and `table_b`.
-
----
-
-## Phase 5: Run Blend Queries
-
-Substitute `<orders_table>` and `<customers_table>` (or equivalent names) in all queries with the resolved table names from Phase 4 (or Phase 2 if skip_upload).
-
-### Query 1 — Join summary (default or custom)
-
-If `join_query` was provided, execute it directly. Otherwise execute the default query, substituting the resolved table names:
-
-```json
-{
-  "namespace_id": "<namespace_id>",
-  "query": "<join_query with table names substituted>"
-}
-```
-
-Use `toolbelt_sql` for this call. Record:
-- `join_rows`: number of rows returned
-- `join_results`: up to 10 rows
-
-### Query 2 — Row counts
-
-Confirm both tables are populated:
-
-```sql
-SELECT '<table_a>' AS table_name, COUNT(*) AS row_count FROM <table_a>
-UNION ALL
-SELECT '<table_b>' AS table_name, COUNT(*) AS row_count FROM <table_b>
-```
-
-Record `row_counts` for each table.
-
-### Query 3 — Unmatched rows check
-
-Identify rows in table A with no match in table B (join integrity check):
-
-```sql
-SELECT COUNT(*) AS unmatched_count
-FROM <table_a> a
-LEFT JOIN <table_b> b ON a.<join_key> = b.<join_key>
-WHERE b.<join_key> IS NULL
-```
-
-Infer `<join_key>` from the shared column names visible in the schema context. If no shared key can be inferred, skip this query and note it in the RESULT.
-
-Record `unmatched_count`.
-
----
-
-## Phase 6: Structured Output
-
-After all phases complete, emit a single structured result:
-
-```
-RESULT:
-  namespace_id: <uuid>
-  phases_run: [0, 1, 2, 3, 4, 5]
-
-  tables:
-    table_a: <sql table name>
-    table_b: <sql table name>
-    row_counts:
-      <table_a>: <count>
-      <table_b>: <count>
-    unmatched_rows: <count or "skipped — no shared key inferred">
-
-  blend_query:
-    sql: |
-      <query executed>
-    row_count: <join_rows>
-    results:
-      - <row 1>
-      - <row 2>
-      ... (up to 10 rows)
-```
-
-If any Phase 5 query fails, include `query_error: "<error>"` under that query's
-section and continue. Only halt on Phase 0–3 failures.
-
----
-
-## Tool Reference
-
-| Phase | Tool(s) |
-|---|---|
-| 0. Verify connection | `toolbelt_list_namespaces` |
-| 1. Resolve namespace | (from Phase 0 result) |
-| 2. Inspect existing tables | `toolbelt_context` |
-| 3. Upload missing tables | `toolbelt_save` |
-| 4. Poll for ingestion | `toolbelt_jobs`, `toolbelt_context` |
-| 5. Run blend queries | `toolbelt_sql`, `toolbelt_execute` |
-| 6. Emit result | (structured output) |

package/sql-analyst/SKILL.md

@@ -1,231 +0,0 @@
----
-name: sql-analyst
-description: >
-  Upload a CSV and answer natural-language questions by generating and executing
-  SQL. Covers totals, averages, group-by, filtering, and single-table joins on
-  tabular data. Use when an agent has structured rows/columns and needs analytical
-  answers — trends, breakdowns, comparisons, rankings. NOT for unstructured
-  documents (use knowledge-graph or vector-search), lat/lon or WKT data (use
-  geo-analyst), live streams (use streaming-analyst), or multi-table JOINs across
-  independent datasets (use data-blend).
-license: MIT
-compatibility: >
-  Requires a Toolbelt account (provision free at https://toolbelt.ai) and an
-  MCP-compatible AI agent (Claude Code, Claude Desktop, OpenClaw, or any client
-  that supports MCP server connections). MCP connection must be pre-established
-  before invocation.
-metadata:
-  author: toolbeltai
-  version: "1.0"
-  homepage: "https://toolbelt.ai/docs/sql"
----
-
-Upload tabular data and answer natural language questions about it using
-Toolbelt MCP tools. Work through each phase in order without prompting for
-user input. On unrecoverable error, emit a structured failure and halt.
-
-## When Not To Use
-
-- For unstructured text or documents — use `knowledge-graph` to extract entities and relationships.
-- For real-time or streaming data — use `streaming-analyst` instead.
-- For spatial data with lat/lon coordinates — use `geo-analyst` instead.
-
-## Invocation Parameters
-
-Extract these from the args string or conversation context before starting:
-
-| Parameter | Required | Description |
-|---|---|---|
-| `namespace_id` | No | UUID of target namespace. Auto-select if omitted and only one exists; fail if ambiguous. |
-| `csv_content` | No | Raw CSV text to upload. Uses the embedded sample dataset if omitted. |
-| `asset_name` | No | Name for the uploaded table asset. Defaults to `sales-data`. |
-| `question` | No | Natural language question to ask about the data. Defaults to `What is the total sales amount by region?` |
-
----
-
-## Default Sample Data
-
-If no `csv_content` is provided, use this sales dataset verbatim:
-
-```
-order_id,date,region,product,category,quantity,unit_price,amount,rep
-1001,2024-01-05,Northeast,Widget Pro,Hardware,12,49.99,599.88,Alice Chen
-1002,2024-01-08,Southeast,Gadget Basic,Software,5,29.99,149.95,Bob Martinez
-1003,2024-01-12,Midwest,Widget Pro,Hardware,8,49.99,399.92,Carol Singh
-1004,2024-01-15,West,Service Plan,Services,3,199.00,597.00,David Park
-1005,2024-01-19,Northeast,Gadget Basic,Software,20,29.99,599.80,Alice Chen
-1006,2024-01-22,West,Widget Pro,Hardware,6,49.99,299.94,Emma Lopez
-1007,2024-02-03,Southeast,Service Plan,Services,2,199.00,398.00,Bob Martinez
-1008,2024-02-07,Midwest,Gadget Plus,Software,15,79.99,1199.85,Frank Kim
-1009,2024-02-11,Northeast,Widget Pro,Hardware,10,49.99,499.90,Alice Chen
-1010,2024-02-14,West,Gadget Basic,Software,8,29.99,239.92,David Park
-1011,2024-02-18,Southeast,Gadget Plus,Software,4,79.99,319.96,Carol Singh
-1012,2024-02-21,Midwest,Service Plan,Services,1,199.00,199.00,Frank Kim
-1013,2024-03-02,Northeast,Service Plan,Services,5,199.00,995.00,Alice Chen
-1014,2024-03-06,West,Gadget Plus,Software,9,79.99,719.91,Emma Lopez
-1015,2024-03-10,Southeast,Widget Pro,Hardware,7,49.99,349.93,Bob Martinez
-1016,2024-03-14,Midwest,Gadget Basic,Software,11,29.99,329.89,Carol Singh
-1017,2024-03-18,Northeast,Gadget Plus,Software,6,79.99,479.94,David Park
-1018,2024-03-22,West,Service Plan,Services,4,199.00,796.00,Emma Lopez
-1019,2024-03-25,Southeast,Widget Pro,Hardware,3,49.99,149.97,Frank Kim
-1020,2024-03-28,Midwest,Widget Pro,Hardware,14,49.99,699.86,Carol Singh
-```
-
-Default `question`: `What is the total sales amount by region?`
-
----
-
-## Phase 0: Verify Connection
-
-Call `toolbelt_list_namespaces` (no arguments) immediately.
-
-- **If it succeeds:** proceed to Phase 1 using the returned namespaces.
-- **If it fails:** emit structured failure and halt.
-
-```
-FAILURE: Toolbelt MCP connection is not established.
-The MCP server must be connected before invoking this skill.
-See: https://toolbelt.ai/docs/mcp for setup instructions.
-```
-
----
-
-## Phase 1: Resolve Namespace
-
-Use the namespaces returned from Phase 0.
-
-Resolution order:
-1. If `namespace_id` was provided as a parameter, use it directly.
-2. If only one namespace exists, use it.
-3. If multiple exist and no `namespace_id` was specified, emit structured failure and halt.
-
-```
-FAILURE: Multiple namespaces found and none specified.
-Available: [<list namespace display names and IDs>]
-Re-invoke with namespace_id=<uuid>.
-```
-
-Store the resolved `namespace_id` — pass it to every subsequent tool call.
-
----
-
-## Phase 2: Upload CSV Data
-
-Resolve `csv_content` (use parameter value or default sample above).
-Resolve `asset_name` (use parameter value or default `sales-data`).
-
-Call `toolbelt_save`:
-
-```json
-{
-  "asset_type": "document",
-  "namespace_id": "<namespace_id>",
-  "name": "<asset_name>",
-  "file_name": "<asset_name>.csv",
-  "content": "<csv_content>",
-  "content_encoding": "text",
-  "data_format": "csv"
-}
-```
-
-Record the returned `asset_id`.
-
----
-
-## Phase 3: Poll for Ingestion
-
-Call `toolbelt_jobs` with `{ "namespace_id": "<namespace_id>" }` every 10 seconds.
-
-Wait for the `ingest` job for this asset to reach `completed`.
-
-Typical duration: 15–60 seconds. Maximum wait: 3 minutes.
-
-If the job reaches `failed` or the timeout elapses, emit structured failure and halt:
-```
-FAILURE: CSV ingestion did not complete.
-Job status: <last observed status>
-```
-
----
-
-## Phase 4: Get Schema Context
-
-Call `toolbelt_context` with `{ "namespace_id": "<namespace_id>" }`.
-
-Locate the table corresponding to the uploaded asset (match by `asset_name` or
-the table name returned from the save call). Record:
-- `table_name`: the SQL table name for this asset
-- `column_names`: list of columns in the table
-- `row_count`: number of rows if provided in context
-
----
-
-## Phase 5: Ask a Natural Language Question
-
-Resolve `question` (use parameter value or default).
-
-Call `toolbelt_search`:
-
-```json
-{
-  "question": "<question>",
-  "namespace_id": "<namespace_id>",
-  "synthesize": true
-}
-```
-
-Parse the response to extract:
-- `answer`: the synthesized natural language answer
-- `sql_generated`: the SQL query that was generated and executed
-- `row_count`: number of rows returned by the SQL query
-- `sources`: any cited source tables or assets
-
-If `toolbelt_search` does not return SQL, try `toolbelt_sql` directly with a
-query you write from the schema context:
-
-```json
-{
-  "namespace_id": "<namespace_id>",
-  "query": "SELECT region, SUM(amount) AS total_amount FROM <table_name> GROUP BY region ORDER BY total_amount DESC"
-}
-```
-
-Record whichever path succeeded as `query_method` (`"search"` or `"direct_sql"`).
-
----
-
-## Phase 6: Structured Output
-
-After all phases complete, emit a single structured result:
-
-```
-RESULT:
-  namespace_id: <uuid>
-  asset_name: <name of uploaded table>
-  table_name: <SQL table name>
-  row_count_ingested: <rows in the table>
-  phases_run: [0, 1, 2, 3, 4, 5]
-
-  question: "<question asked>"
-  query_method: "<'search' or 'direct_sql'>"
-  sql_generated: |
-    <SQL query that was generated or executed>
-  row_count: <number of rows returned by the query>
-  answer: |
-    <synthesized answer>
-  sources: [<cited tables or assets>]
-```
-
----
-
-## Tool Reference
-
-| Phase | Tool(s) |
-|---|---|
-| 0. Verify connection | `toolbelt_list_namespaces` |
-| 1. Resolve namespace | (from Phase 0 result) |
-| 2. Upload CSV document | `toolbelt_save` |
-| 3. Poll for ingestion | `toolbelt_jobs` |
-| 4. Get schema context | `toolbelt_context` |
-| 5. Ask question | `toolbelt_search`, `toolbelt_sql` (fallback) |
-| 6. Emit result | (structured output) |