القائمة
Discover what's in the connected warehouse — schemas, tables, columns, and CARTO named sources.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Author, edit, publish, and validate CARTO Builder maps via the `carto maps` CLI. Use when the user wants to create a map from a natural-language request, edit an existing map (datasets, layers, styling, privacy, popups, widgets, SQL parameters), duplicate one, upload custom marker icons, or wire up an AI agent on a map. Covers the full `carto maps` subcommand surface — `list`, `get`, `create`, `update`, `delete`, `publish`, `validate`, `schema`, `agents`, `markers`, `screenshot`, `datasets update`.
Start here for first-time CARTO use — install the CLI, authenticate, switch profiles, understand JSON output and async job patterns. Also orients on the two parallel access paths into the CARTO platform (CLI for authoring/scripting, MCP server for inline interactions in chat hosts) and which skills cover each.
Administer the CARTO org — users, roles, quotas, activity audit, and bulk resource operations.
Write spatial SQL against the connected warehouse — dialect-specific guidance, performance defaults, and CARTO's query/job execution model.
Generate a working geospatial app powered by CARTO and deck.gl — basemap, layers (vector / H3 / quadbin / raster), widgets, filters, legend, inputs, optional chat-with-map agent, and the right auth strategy (public token, OAuth, SSO, or M2M).
Render an ad-hoc interactive map inline in the chat from a deck.gl declarative spec via the CARTO MCP server's view_map tool. Use whenever the user asks to map, visualize, or show the geographic distribution of points, polygons, hexagons, quadbins, clusters, density (heatmaps), or raster — and the map is exploratory or throwaway, not meant to be saved as a permanent CARTO Builder map. Triggers on "show me X on a map", "visualize Y", "make a heatmap of Z", "render the points/clusters/raster of W". Distinct from carto-create-builder-maps (CLI authoring of permanent maps), carto-preview-builder-map (loading an existing saved Builder map), and carto-develop-app (writing a from-scratch deck.gl app in TypeScript / JavaScript).
استنادا إلى تصنيف SOC المهني
| name | carto-explore-datawarehouse |
| description | Discover what's in the connected warehouse — schemas, tables, columns, and CARTO named sources. |
| license | MIT |
Before writing SQL or building maps, an agent typically needs to know what's in the warehouse. This skill covers two CARTO surfaces for that:
carto connections browse — walk the warehouse hierarchy (project → dataset → table).carto connections describe — inspect a specific table's columns and types.And one CARTO-specific concept:
If you already know the table and just want to query it, jump straight to carto-query-datawarehouse.
# What connections are registered?
carto connections list --json
# Walk the hierarchy (no path = top level)
carto connections browse <connection-name>
# Drill in
carto connections browse <connection-name> "carto-demo-data"
carto connections browse <connection-name> "carto-demo-data.demo_tables"
# Get columns + types for a specific table
carto connections describe <connection-name> "carto-demo-data.demo_tables.nyc_collisions"
The exact path syntax depends on the engine:
| Engine | browse path shape |
|---|---|
| BigQuery | project.dataset.table |
| Snowflake | DATABASE.SCHEMA.TABLE |
| Postgres / Redshift | schema.table (no leading project/database) |
| Databricks | catalog.schema.table |
| Topic | Reference |
|---|---|
connections browse and connections describe in detail | references/connection-browse.md |
| Named sources — what they are, how to list and inspect them | references/named-sources.md |
connections browse usually saves a five-minute "table not found" loop.--page-size when a dataset has hundreds of tables; the default is 30.describe returns column types — use those types to write correct SQL (e.g. don't ST_DWithin against a STRING column the user mistakenly named geom).carto-demo-data is a public BigQuery dataset CARTO ships — carto connections browse <bq-connection> "carto-demo-data" works on any BigQuery connection that has the right IAM, and is a fast way to validate a fresh connection without touching customer data.