Install
$ agentstack add skill-cartodb-agent-skills-carto-find-spatial-data ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
carto-find-spatial-data
The CARTO Data Observatory (DO) is a catalog of curated external spatial datasets — demographics, points of interest, environmental data, mobility, financial — that you can subscribe to and have materialized into your own data warehouse. Instead of the user hunting down a US census shapefile, this skill answers: "what's already curated in the DO that would help here?"
This skill covers discovery and subscription. Once subscribed, the data lives in the user's warehouse and is queryable like any other table — see [carto-query-datawarehouse](../carto-query-datawarehouse).
When to use this skill
- The user asks for "demographics", "points of interest", "boundaries", "mobility data", "weather", or any other category of external spatial data.
- The user has internal data and wants to enrich it with external context (e.g., spatial-join their stores against census tracts).
- The user is exploring what's available before committing to a paid subscription.
If the user already has the dataset in their warehouse, jump to [carto-explore-datawarehouse](../carto-explore-datawarehouse) instead — DO is for sourcing new external data.
Quick reference
# Discover what's available — by keyword
carto do search --keyword "census" --json
carto do search --keyword "weather" --country usa --json
# Inspect a specific dataset
carto do get --json
# List your active subscriptions
carto do subscriptions list --json
# Subscribe (writes to a connection in your org)
carto do subscribe \
--connection carto_dw \
--destination my_project.do.census_tracts
> The exact carto do subcommand surface is evolving — search, get, subscribe, subscriptions are the stable verbs. Check carto do --help if a flag isn't recognized.
What's in this skill
| Topic | Reference | |---|---| | Discovery: searching, filtering, evaluating datasets | [references/data-observatory.md](references/data-observatory.md) | | Subscribing: paid vs free, materialization, refresh, costs | [references/subscribe.md](references/subscribe.md) |
Always-on guidance
- Free vs paid: many DO datasets are free (US Census, OpenStreetMap-derived, NaturalEarth). Premium datasets (Spatial.ai, Mastercard, AirSage, etc.) require a CARTO subscription contract —
carto do getshows the licensing and pricing tier. - Subscription lands data into the user's warehouse. It's not a remote view — actual rows are written to a destination table the user pays warehouse storage for. Plan destination naming accordingly.
- Spatial extension required. DO datasets often include H3 cells / geometry types that depend on CARTO's spatial extension being installed in the destination warehouse. If subscribing fails with "function not found", check that the spatial extension is installed — see [
carto-manage-platform](../carto-manage-platform). - Don't recommend a DO dataset without
carto do getfirst. The dataset's metadata reveals coverage (US-only, EU-only, global), update cadence (monthly, yearly, real-time), and licensing — all critical to whether it actually fits the user's question. - **DO is external; named sources are internal.** Don't confuse the two. Named sources (covered in [
carto-explore-datawarehouse/references/named-sources.md](../carto-explore-datawarehouse/references/named-sources.md)) are the user's saved queries; DO is the curated catalog of third-party data.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: CartoDB
- Source: CartoDB/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.