القائمة
Choose and configure the data warehouse engine connection for CARTO (BigQuery, Snowflake, Redshift, Postgres, Databricks, Oracle).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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).
| name | carto-connect-datawarehouse |
| description | Choose and configure the data warehouse engine connection for CARTO (BigQuery, Snowflake, Redshift, Postgres, Databricks, Oracle). |
| license | MIT |
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.
Use carto-explore-datawarehouse once a connection exists and you want to inspect what's inside it.
carto connections list --json # what's already connected?
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)
connections list and connections get are non-destructive — agents should run them freely before deciding what to do.
| Engine | When to choose it | Reference |
|---|---|---|
| BigQuery | Google Cloud users; CARTO's flagship integration; rich GIS functions native. | references/bigquery.md |
| Snowflake | Snowflake-shop customers; geospatial via SQL functions and Snowflake-native types. | references/snowflake.md |
| Redshift | AWS-shop customers on Redshift Serverless or RA3 clusters. | references/redshift.md |
| Postgres | Self-hosted or RDS Postgres with PostGIS; common for small/medium deployments. | references/postgres.md |
| Databricks | Lakehouse / Unity Catalog users; SQL Warehouses recommended for interactive workloads. | references/databricks.md |
| Oracle | Oracle Database with Spatial; on-prem or OCI / Autonomous Database deployments. | references/oracle.md |
If the user already has a connection (
connections listreturns at least one), don't push a new one — use the existing one.
carto connections list # default page (10)
carto connections list --all # all pages
carto connections list --search "prod" # filter by name
carto connections list --json # machine-readable
connections describe and table reads come from the credential CARTO holds, not from the user's CARTO role. A CARTO Admin with a low-privilege service account will still see "permission denied" from the warehouse.carto-explore-datawarehouse.carto-query-datawarehouse.carto-import-export-data.