# Skills catalog The CARTO Agent Skills catalog ships **23 skills** organized in three tiers. The list below is a snapshot; the canonical, always-up-to-date catalog is [`skills/catalog.json`](https://github.com/CartoDB/agent-skills/blob/master/skills/catalog.json) in the public repo. ## Utility tier Foundational CARTO primitives. No dependencies; loaded by other skills as a shared base. | Skill | Description | | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | [`carto-basics`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-basics) | Start here for first-time CARTO CLI use: install, authenticate, switch profiles, understand JSON output and async job patterns. | | [`carto-connect-datawarehouse`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-connect-datawarehouse) | Choose and configure the data warehouse engine connection (BigQuery, Snowflake, Redshift, Postgres, Databricks). | | [`carto-query-datawarehouse`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-query-datawarehouse) | Write spatial SQL against the connected warehouse engine, with dialect-specific guidance and performance defaults. | | [`carto-explore-datawarehouse`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-explore-datawarehouse) | Discover what's in the connected warehouse: schemas, tables, columns, named sources. | ## Platform tier CARTO product surfaces. Depend only on utility skills. | Skill | Description | | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`carto-import-export-data`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-import-export-data) | Import geospatial files into the data warehouse via CARTO, export results back out, and prepare tilesets for fast map rendering. | | [`carto-create-workflow`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-create-workflow) | Build, schedule, and operate analytics DAGs in CARTO Workflows — the no-code/low-code orchestration layer over the data warehouse. Triggers when the user wants to author a workflow, run/edit one, or schedule a DAG. | | [`carto-find-spatial-data`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-find-spatial-data) | Discover and subscribe to external spatial datasets via CARTO Data Observatory and partner catalogs. | | [`carto-manage-platform`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-manage-platform) | Administer the CARTO org — users, roles, quotas, activity audit, and bulk resource operations. | | [`carto-create-builder-maps`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-create-builder-maps) | Author maps in CARTO Builder via the CLI: layers, basemaps, styling, sharing, and AI Agents. | | [`carto-render-inline-map`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-render-inline-map) | 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. For exploratory / throwaway visualizations; triggers on "show me X on a map", "visualize Y", "make a heatmap of Z". | | [`carto-preview-builder-map`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-preview-builder-map) | Preview an existing saved CARTO Builder map inline in the chat via the CARTO MCP Server's `load_builder_map` tool. Resolves URL / ID / name (via `list_maps`), renders a lightweight read-only preview. Triggers on "show me the X map", "open the Y map", and post-CLI-creation inline previews. | | [`carto-develop-app`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-develop-app) | Generate a working geospatial application 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). | ## Use-case tier Recipe skills that compose platform skills into end-to-end spatial analyses. Each carries trigger keywords so the agent routes on user intent. | Skill | Description & triggers | | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`carto-hotspot-analysis`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-hotspot-analysis) | Builds Getis-Ord Gi\* hotspot analysis workflows. Triggers on: hotspots, coldspots, spatial clusters, Getis-Ord, Gi\*, cluster detection, concentration areas, spacetime hotspot, temporal clusters, time-varying patterns, hotspot trends, emerging hotspots, Mann-Kendall. | | [`carto-spatial-autocorrelation`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-spatial-autocorrelation) | Builds Moran's I spatial autocorrelation workflows. Triggers on: spatial autocorrelation, Moran's I, spatial dependency, HH/HL/LH/LL quadrants, LISA, spatial weight matrix, classifying locations into cluster types. | | [`carto-gwr`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-gwr) | Builds Geographically Weighted Regression (GWR) workflows. Triggers on: GWR, geographically weighted regression, spatially varying relationships, local regression, local coefficients, spatial non-stationarity. | | [`carto-spatial-enrichment`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-spatial-enrichment) | Spatial enrichment workflows. Triggers on: enrich, add demographics, estimate population around locations, compute spatial features, sociodemographic analysis, trade-area enrichment. | | [`carto-trade-area-analysis`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-trade-area-analysis) | Trade area and catchment analysis. Triggers on: trade area, catchment area, isochrone, drive time, walk time, billboard placement, OOH audience targeting, scoring candidate locations. | | [`carto-site-selection`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-site-selection) | Site selection and cannibalization analysis. Triggers on: site selection, cannibalization, new store location, optimal location, twin areas, look-alike areas. | | [`carto-territory-planning`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-territory-planning) | Territory planning combining territory balancing and location allocation. Triggers on: sales territories, service zones, balanced territories, location allocation, depot/hub placement, response-time optimization, demand coverage. | | [`carto-routing-od-analysis`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-routing-od-analysis) | Routing and origin-destination analysis. Triggers on: routing, travel time, OD matrix, isoline, isochrone, catchment area, drive-time polygon, accessibility analysis, commute patterns, OD flow, shortest-path computation. | | [`carto-geocoding`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-geocoding) | Geocoding workflows that convert addresses or place names into coordinates. Triggers when the user has tabular data with addresses but no geometry column. | | [`carto-composite-scoring`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-composite-scoring) | Composite-score workflows. Triggers on: composite scores, indexes, multi-variable rankings, market potential, resilience indexes, risk indexes, weighted scores, PCA, supervised/unsupervised scoring. | | [`carto-arcgis-migration`](https://github.com/CartoDB/agent-skills/tree/master/skills/carto-arcgis-migration) | End-to-end ArcGIS Portal / AGOL to CARTO migration. Three phases over a shared `MIGRATION_MANIFEST.md`: discover (enumerate and classify items), migrate-data (Hosted Feature Layers / Tables → CARTO tables), migrate-maps (Web Maps and simple Dashboard / Web Experience / Web Mapping Application entries → CARTO Builder maps). Default mode is batch; migrated maps are tagged `From ArcGIS` and created as private. Triggers when the user wants to migrate ArcGIS content to CARTO, asks "what's in my Portal", or names a Portal/AGOL URL. | ## Dependencies and routing Use-case skills depend on `carto-create-workflow`. Platform skills depend on the relevant utility skills (e.g. `carto-create-workflow` depends on `carto-basics`, `carto-connect-datawarehouse`, and `carto-query-datawarehouse`; `carto-render-inline-map` and `carto-preview-builder-map` depend only on `carto-basics`). When a use-case skill is triggered, the agent loads it along with its dependency chain. Routing happens via skill descriptions and trigger keywords (the catalog descriptions above). Phrasing your request with one of the trigger keywords is the most reliable way to route into a specific skill. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.carto.com/carto-for-agents/agent-skills/skills-catalog.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.