carto-explore-datawarehouse

• carto connections browse

  — walk the warehouse hierarchy (project → dataset → table).

• carto connections describe

  — inspect a specific table's columns and types.

• Named sources — saved, parameterized SQL that maps and apps consume as if they were tables.

When to use this skill

• You don't know which tables / schemas exist in a connection.
• You need a column list and types before writing SQL or authoring a map.
• The user references "the named source for X" and you need to find it.

carto-query-datawarehouse

Quick reference

# 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"

browse

project.dataset.table

DATABASE.SCHEMA.TABLE

schema.table

catalog.schema.table

What's in this skill

connections browse

connections describe

Always-on guidance

• Browse before you query. A two-second

  connections browse

  usually saves a five-minute "table not found" loop.
• Use

  --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

  ).
• Named sources ≠ tables. They're parameterized queries. Inspect the underlying tables before assuming a column you see in the source exists in raw form.

• 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.