eddietejeda · Aug 1, 2026
@@ -76,7 +76,6 @@ pre-release-hook = ["git-cliff", "--unreleased", "--tag", "v{{version}}", "--pre
 publish = false
 pre-release-replacements = [
   { file = "skills/hotdata/SKILL.md", search = "^version: .+", replace = "version: {{version}}", exactly = 1 },
-  { file = "skills/hotdata-search/SKILL.md", search = "^version: .+", replace = "version: {{version}}", exactly = 1 },
   { file = "skills/hotdata-analytics/SKILL.md", search = "^version: .+", replace = "version: {{version}}", exactly = 1 },
   { file = "skills/hotdata-geospatial/SKILL.md", search = "^version: .+", replace = "version: {{version}}", exactly = 1 },
   # README.md no longer carries a hardcoded version badge — it tracks GitHub releases.

@@ -1,16 +1,16 @@
 ---
 name: hotdata-analytics
-description: Use this skill when the user wants OLAP-style SQL analytics in Hotdata — aggregations, GROUP BY, JOINs, reporting, exploratory queries, query run history, stored results, or materialized follow-up tables (Chain into managed databases). Activate for "analyze", "aggregate", "rollup", "pivot", "report", "metrics", "GROUP BY", "query history", "past queries", "query runs", "stored results", "materialize", "chain", "intermediate table", or sorted indexes for filters/range scans. Do not load for BM25/vector search or geospatial SQL — use hotdata-search or hotdata-geospatial. Requires the core hotdata skill for tables and auth.
+description: Use this skill when the user wants OLAP-style SQL analytics in Hotdata — aggregations, GROUP BY, JOINs, reporting, exploratory queries, query run history, stored results, or materialized follow-up tables (Chain into managed databases). Activate for "analyze", "aggregate", "rollup", "pivot", "report", "metrics", "GROUP BY", "query history", "past queries", "query runs", "stored results", "materialize", "chain", "intermediate table", or sorted indexes for filters/range scans. Do not load for BM25/vector search or geospatial SQL — use the core hotdata skill (search section) or hotdata-geospatial. Requires the core hotdata skill for tables and auth.
 version: 0.21.0
 ---
 
 # Hotdata Analytics Skill
 
 **OLAP-style analytics** in Hotdata: PostgreSQL-dialect SQL, query execution, run history, stored results, **Chain** materializations, and **sorted** indexes for filters and joins.
 
-**Prerequisites:** Authenticate, workspace, and catalog discovery via the **`hotdata`** skill (`connections`, `tables`, `databases`).
+**Prerequisites:** Authenticate, workspace, and catalog discovery via the **`hotdata`** skill (`tables`, `databases`; attach a connection as a queryable catalog with `databases attach`).
 
-**Related skills:** **`hotdata-search`** (BM25, vector, retrieval indexes), **`hotdata-geospatial`** (spatial SQL).
+**Related skills:** the core **`hotdata`** skill (BM25/vector search + retrieval indexes), **`hotdata-geospatial`** (spatial SQL).
 
 ---
 
@@ -103,7 +103,7 @@ Full procedure: [references/WORKFLOWS.md](references/WORKFLOWS.md).
 
 ## Sorted indexes (filters and range scans)
 
-For equality, range, and sort-heavy OLAP — not full-text or vector (see **`hotdata-search`**):
+For equality, range, and sort-heavy OLAP — not full-text or vector (see the core **`hotdata`** skill → Search & retrieval indexes):
 
 ```bash
 hotdata indexes create --catalog <catalog-alias> --schema <schema> --table <table> \

@@ -2,7 +2,7 @@
 
 OLAP-style SQL, **History** (query runs and stored results), and **Chain** (materialized follow-ups). Requires **`hotdata`** for auth, workspaces, and catalog commands.
 
-**Related:** **`hotdata-search`** for BM25/vector indexes and `hotdata search`; **`hotdata`** [WORKFLOWS.md](../../hotdata/references/WORKFLOWS.md) for managed databases.
+**Related:** the core **`hotdata`** skill for BM25/vector indexes and `hotdata search`; **`hotdata`** [WORKFLOWS.md](../../hotdata/references/WORKFLOWS.md) for managed databases.
 
 ---
 
@@ -24,7 +24,7 @@ hotdata queries <query_run_id>
 - `<query_run_id>` — full metadata (timings, `result_id`, snapshot, hashes) and formatted SQL.
 - If a run has a `result_id`, fetch rows with `hotdata results <result_id>` below.
 
-Use history to spot recurring `WHERE`, `JOIN`, `GROUP BY`, or search-style SQL before adding indexes (**`hotdata-search`**) or new Chain tables.
+Use history to spot recurring `WHERE`, `JOIN`, `GROUP BY`, or search-style SQL before adding indexes (core **`hotdata`** skill) or new Chain tables.
 
 ### Stored results
 

@@ -8,7 +8,7 @@ version: 0.21.0
 
 Hotdata supports a subset of PostGIS-style functions in **PostgreSQL-dialect SQL**. This skill is data-agnostic — apply it to any table with geometry columns.
 
-**Requires the core `hotdata` skill** for auth, workspace, and table discovery. **Related:** **`hotdata-analytics`** (OLAP SQL), **`hotdata-search`** (BM25/vector).
+**Requires the core `hotdata` skill** for auth, workspace, table discovery, and **search/retrieval indexes** (BM25/vector). **Related:** **`hotdata-analytics`** (OLAP SQL).
 
 ## Running these queries
 
@@ -20,7 +20,7 @@ hotdata query "<sql>" [--workspace-id <id>] [--database <db>] [--output table|js
 
 - **Fully qualify tables** as `<connection>.<schema>.<table>` (or `<catalog>.<schema>.<table>` for a managed database) — every `<table>` placeholder below means a qualified name.
 - **PostgreSQL dialect:** double-quote any non-lowercase identifier (e.g. `"GeoID"`).
-- Discover candidate tables/columns with **`hotdata tables list --connection-id <id>`** (connection tables) or **`hotdata databases tables`** (tables inside a managed database) — see core skill.
+- Discover candidate tables/columns with **`hotdata tables list`** (all workspace tables; narrow with `--schema`/`--table` wildcards) or **`hotdata databases tables list`** (tables inside a managed database), then inspect column types with **`hotdata tables show <catalog.schema.table>`** — see core skill.
 
 ---
 
@@ -46,7 +46,7 @@ wkb_geometry_bbox['xmin']   -- ✓ works
 (wkb_geometry_bbox).xmin    -- ✗ not supported
 ```
 
-Find these columns by their `Binary` / `Struct` types in `hotdata tables list --connection-id <id>`.
+Find these columns by their `Binary` / `Struct` types with `hotdata tables show <catalog.schema.table>` (or scan `hotdata tables list`).
 
 ---
 
@@ -155,7 +155,7 @@ SELECT <id_col>, ST_AsText(ST_Simplify(ST_GeomFromWKB(wkb_geometry), 0.0001)) AS
 
 ## Workflow: explore a new geospatial table
 
-1. **Find geometry columns** — `hotdata tables list --connection-id <id>`; look for `Binary` (WKB) / `Struct` (bbox) types.
+1. **Find geometry columns** — `hotdata tables list`, then `hotdata tables show <catalog.schema.table>`; look for `Binary` (WKB) / `Struct` (bbox) types.
 2. **Geometry types** — run the "Geometry types in a table" pattern above.
 3. **Coverage / extent** — aggregate the bbox struct:
    ```sql