skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
cartodb/agent-skills59 installs

carto-connect-datawarehouse

Choose and configure the data warehouse engine connection for CARTO (BigQuery, Snowflake, Redshift, Postgres, Databricks, Oracle).

How do I install this agent skill?

npx skills add https://github.com/cartodb/agent-skills --skill carto-connect-datawarehouse
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a legitimate configuration guide for the CARTO platform that helps users set up data warehouse connections. It follows best practices for credential management and uses official tools without any malicious behavior.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

carto-connect-datawarehouse

CARTO runs spatial analytics in the user's own data warehouse. A connection is the bridge between CARTO and that warehouse: it carries credentials, target project/database scoping, and sometimes a service account or PAT. Most other CARTO operations (querying, importing, building maps, running workflows) require an existing connection.

TaskMCPCLI (fallback)
List / inspect connectionsexplore_data (list_connections on any session; get_connection is OAuth-only)carto connections list / get
Create / update a connectionmanage_connections (create, update) — OAuth session onlycarto connections create / update
Delete a connectiondelete (kind=connection) — OAuth session onlycarto connections delete

Access-path routing. With the MCP server attached, list over explore_data (list_connections); create/update over manage_connections; delete over delete. On a token session only list_connections is available — get_connection and the write tools (manage_connections, delete) need OAuth, so fall back to the carto connections CLI. Also use the CLI when the server isn't attached or for scripted setups. The engine-choice guidance and pitfalls below apply on either path. Detection signals: carto-basics/references/access-paths.md.

When to use this skill

  • The user wants to connect a new warehouse to CARTO.
  • The user is debugging a connection (auth failures, missing tables, permission errors).
  • A downstream skill needs a connection name and you don't yet know which engine the user has.
  • The user is rotating credentials or moving from one project/database to another.

Use carto-explore-datawarehouse once a connection exists and you want to inspect what's inside it.

Quick lifecycle (CLI)

carto connections list --json             # what's already connected? (--all, --search "prod")
carto connections get <id>                # detailed view of one connection
carto connections create                  # interactive create
carto connections update <id>             # rotate credentials, change scoping
carto connections delete <id>             # remove (irreversible)

List/inspect are non-destructive — run them freely before deciding what to do. If the user already has a connection, don't push a new one — use the existing one.

Choosing an engine

EngineWhen to choose itReference
BigQueryGoogle Cloud users; CARTO's flagship integration; rich GIS functions native.references/bigquery.md
SnowflakeSnowflake-shop customers; geospatial via SQL functions and native types.references/snowflake.md
RedshiftAWS-shop customers on Redshift Serverless or RA3 clusters.references/redshift.md
PostgresSelf-hosted or RDS Postgres with PostGIS; common for small/medium deployments.references/postgres.md
DatabricksLakehouse / Unity Catalog users; SQL Warehouses for interactive workloads.references/databricks.md
OracleOracle Database with Spatial; on-prem or OCI / Autonomous Database.references/oracle.md

Common pitfalls

  • Auth-mode mismatch: BigQuery supports OAuth (interactive) and service-account JSON (CI). Pick one consistently per environment; mixing the two breaks shared connections.
  • Region vs project: Some engines need both an account/project and a region (Snowflake, Redshift). Skipping the region typically yields "endpoint not found" rather than a permissions error.
  • Default database/schema scoping: CARTO writes tilesets, named sources, and analytics output back into the warehouse. Confirm which dataset/schema CARTO may write to before creating the connection.
  • Permissions for describe and table reads come from the credential CARTO holds, not the user's CARTO role. A CARTO Admin with a low-privilege service account still sees "permission denied" from the warehouse.

What this skill doesn't cover

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/cartodb/agent-skills/carto-connect-datawarehouse">View carto-connect-datawarehouse on skillZs</a>