carto-query-datawarehouse
Installation
SKILL.md
carto-query-datawarehouse
Run SQL — spatial or otherwise — against any connection CARTO has registered. Two execution surfaces, matched across MCP and CLI:
Row-returning SELECT (1-min timeout) |
DDL/DML & long queries (no timeout, no rows) | |
|---|---|---|
| MCP (primary) | execute_query |
execute_async_query (submit/status/cancel) |
| CLI (fallback) | carto sql query |
carto sql job |
Access-path routing. With the CARTO MCP server attached, run SQL through
execute_queryandexecute_async_query— both available even on token-authenticated sessions. The dialect guidance and performance rules here apply identically on either path. Use thecarto sqlCLI when the server isn't attached or the SQL is scripted/CI.carto activity query(local DuckDB over downloaded activity data) is CLI-only — no MCP equivalent. Detection signals:carto-basics/references/access-paths.md.
When to use this skill
- The user wants to count rows, run an exploratory
SELECT, or build a transformation. - The user is debugging slow / failing SQL.
- The agent needs to materialize an intermediate table before authoring a map.
- The user wants an ad-hoc spatial join, buffer, or H3 aggregation.