القائمة
How to use the CARTO CLI to interact with the platform
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to write, validate, and upload CARTO Workflows
How to enrich component notes and input type documentation served by the local workflows-api
Builds Geographically Weighted Regression (GWR) workflows in CARTO. Triggers when the user mentions GWR, geographically weighted regression, spatially varying relationships, local regression, local coefficients, spatial regression, "what drives X in different areas", "why do prices vary spatially", "local factors affecting Y", varying coefficients, coefficient maps, spatial non-stationarity, or wants to model how the relationship between a dependent variable and predictors changes across geography. Produces per-cell regression coefficients that reveal how predictor importance shifts from place to place.
Builds Getis-Ord Gi* hotspot analysis workflows in CARTO. Triggers when the user mentions hotspots, coldspots, spatial clusters, Getis-Ord, Gi*, cluster detection, concentration areas, "where do X cluster", spacetime hotspot, temporal clusters, time-varying patterns, hotspot trends, emerging hotspots, Mann-Kendall, or wants to find statistically significant spatial or spatiotemporal patterns in point or grid data.
Builds Moran's I spatial autocorrelation workflows in CARTO. Triggers when the user mentions spatial autocorrelation, Moran's I, spatial dependency, spatial correlation, spatial outliers, HH HL LH LL quadrants, high-high clusters, low-low clusters, spatial weight matrix, "is there clustering", "are values spatially correlated", local indicators of spatial association, LISA, spatial randomness test, or wants to determine whether a variable exhibits spatial clustering, dispersion, or randomness across a gridded dataset. Also relevant when the user needs to classify locations into cluster types (HH, HL, LH, LL) rather than just identifying hotspots and coldspots.
Guides building ML pipelines in CARTO Workflows when the user wants to train a model, predict, classify, forecast, or do regression. Triggers on machine learning, ML, prediction, classification, regression, forecasting, churn, predict, train model, BigQuery ML, Snowflake ML, BQML, ARIMA, time series prediction.
| name | carto-cli |
| description | How to use the CARTO CLI to interact with the platform |
The carto CLI is the command-line interface for the CARTO platform. This skill provides quick reference and links to detailed documentation for each command group.
Version: 0.5.0
| Task | Command |
|---|---|
| Check auth | carto auth status |
| Login | carto auth login |
| List connections | carto connections list |
| Describe table | carto connections describe <conn> "<fqn>" |
| Run query | carto sql query <conn> "<sql>" |
| Execute DDL/DML | carto sql job <conn> "<sql>" |
| Validate workflow (offline) | carto workflows validate file.json --json |
| Validate workflow (deep, warehouse-aware) | carto workflows verify file.json --connection <conn> --json |
| Generate SQL | carto workflows to-sql file.json --connection <conn> |
| List components | carto workflows components list --connection <conn> --json |
| Get component schema | carto workflows components get <names> --connection <conn> --json |
| Get input type formats | carto workflows components get <names> --connection <conn> --input-formats --json |
| Upload workflow | carto workflows create --file file.json --verify |
| List workflows | carto workflows list --json |
| Update workflow | carto workflows update <id> --file file.json |
| Delete workflow | carto workflows delete <id> |
| Import file | carto imports create --file <path> --connection <conn> --destination "<fqn>" |
| Group | Description | Details |
|---|---|---|
| auth | Authentication and profiles | Login, logout, status, profile switching |
| connections | Data connections | List, browse, describe tables |
| sql | SQL execution | Query and job commands |
| workflows | Workflow operations | Validate, to-sql, components, schedules |
| imports | Data import | Upload files to tables |
| install | Installation | Build CLI from source |
These flags work with all commands:
| Flag | Description |
|---|---|
--json | Output in JSON format (recommended for parsing) |
--debug | Show request details (method, URL, headers) |
--yes, -y | Skip confirmation prompts (for automation) |
--profile <name> | Use specific profile (default: "default") |
--token <token> | Override API token |
--base-url <url> | Override base API URL |
Environment Variables:
CARTO_API_TOKEN - API token for authenticationCARTO_PROFILE - Profile to use (overrides current_profile)| Issue | Cause | Solution |
|---|---|---|
workflows validate misses column errors | validate is offline/Zod-only — use workflows verify --connection <conn> for warehouse-aware checks | |
workflows components list fails | Missing connection | Add --connection <name> |
connections browse --page-size ignored | Known limitation | Use head -n N or query INFORMATION_SCHEMA |
| Table path not found | Unquoted path | Quote paths with dots: "project.dataset.table" |
| Token expired | Session timeout | Run carto auth login |
| Delete command hangs | Waiting for confirmation | Type "delete" or use --yes flag |
Always verify authentication first:
carto auth status
If not authenticated or token expired, run carto auth login (opens browser).