메뉴
Administer the CARTO org — users, roles, quotas, activity audit, and bulk resource operations.
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.
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).
Guides the user through building composite score workflows when they ask about composite scores, indexes, multi-variable scores, ranking areas, site scoring, market potential, resilience indexes, risk indexes, weighted scores, PCA, or supervised/unsupervised scoring.
| name | carto-manage-platform |
| description | Administer the CARTO org — users, roles, quotas, activity audit, and bulk resource operations. |
| license | MIT |
Org-level operations: managing users and invitations, monitoring quotas, auditing activity, and superadmin bulk ops on resources. Most of these commands require Admin or Superadmin role; non-admin users will see permission errors.
For querying activity data interactively (the exploratory side), use carto-query-datawarehouse/references/activity-queries.md. This skill is for the operational/admin surface around activity data.
# Org overview (users, resources, quotas, AI limits)
carto org stats
# User management
carto users list --all --json
carto users invite alice@example.com --role Builder
carto users get alice@example.com
# Activity audit (Enterprise Large+)
carto activity export \
--start-date 2026-04-01 --end-date 2026-04-28 \
--output-dir ./apr-2026
# Superadmin bulk
carto admin list maps --all
carto admin batch-delete
carto admin transfer
| Topic | Reference |
|---|---|
org stats and quota monitoring | references/org-and-quotas.md |
users lifecycle: list, invite, role changes, deletion with handoff | references/users-and-invites.md |
admin superadmin ops: bulk list, batch delete, resource transfer | references/admin-bulk-ops.md |
| Activity event-type catalog (150+ events; full reference) | references/activity-event-reference.md |
| Advanced activity analyses (success rates, trends, by-category) | references/advanced-analyses.md |
| Activity-data troubleshooting (DuckDB install, plan gates, TLS) | references/activity-troubleshooting.md |
users delete if the receiver-id isn't valid. Pass valid emails or user IDs; check via users get first.users delete requires a receiver to inherit the deleted user's resources. Without a receiver argument, the command fails. Plan handoff before deletion: carto users delete <departing-user> <receiving-user>.org stats shows what you can see. Some fields (AI limits, billing) only render for Admin/Superadmin. Don't assume the absence of a field means the resource doesn't exist.admin batch-delete deletes the listed resource IDs without further confirmation per item. Double-check the input list, or do a dry-run with admin list first.activity events, not the CLI return values. To answer "who deleted map X", query the MapDeleted events — see the activity-queries reference.