Ops Telemetry Query
boundless-xyz/boundless
Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.
Answer questions about spatial data using DuckDB. An agent skill from duckdb/duckdb-skills.
$ npx skills add duckdb/duckdb-skills --skill spatial -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install duckdb/duckdb-skills spatial --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/duckdb/duckdb-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spatial .claude/skills/spatial && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spatial" agent skill from https://github.com/duckdb/duckdb-skills/tree/main/skills/spatial into .claude/skills/spatial/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spatial", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/duckdb/duckdb-skills/tree/main/skills/spatialType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add duckdb/duckdb-skills --skill spatial -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install duckdb/duckdb-skills spatial --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/duckdb/duckdb-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spatial .agents/skills/spatial && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spatial" agent skill from https://github.com/duckdb/duckdb-skills/tree/main/skills/spatial into .agents/skills/spatial/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spatial", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add duckdb/duckdb-skills --skill spatial -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install duckdb/duckdb-skills spatial --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/duckdb/duckdb-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spatial .cursor/skills/spatial && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spatial" agent skill from https://github.com/duckdb/duckdb-skills/tree/main/skills/spatial into .cursor/skills/spatial/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spatial", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/duckdb/duckdb-skills.git --path skills/spatial--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add duckdb/duckdb-skills --skill spatial -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install duckdb/duckdb-skills spatial --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/duckdb/duckdb-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spatial .gemini/skills/spatial && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spatial" agent skill from https://github.com/duckdb/duckdb-skills/tree/main/skills/spatial into .gemini/skills/spatial/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spatial", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install duckdb/duckdb-skills spatialInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add duckdb/duckdb-skills --skill spatial -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/duckdb/duckdb-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spatial .github/skills/spatial && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spatial" agent skill from https://github.com/duckdb/duckdb-skills/tree/main/skills/spatial into .github/skills/spatial/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spatial", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add duckdb/duckdb-skills --skill spatial -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install duckdb/duckdb-skills spatial --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/duckdb/duckdb-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spatial .opencode/skills/spatial && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spatial" agent skill from https://github.com/duckdb/duckdb-skills/tree/main/skills/spatial into .opencode/skills/spatial/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spatial", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
spatialAnswer questions about spatial data using DuckDB. An agent skill from duckdb/duckdb-skills.
Spatial is an agent skill from duckdb/duckdb-skills, published by the product's own GitHub organization. Answer questions about spatial data using DuckDB. Use when the user mentions locations, coordinates, lat/lng, distances, maps, addresses, "near", "within", "closest", geographic names, or spatial file formats (GeoJSON, Shapefile, GeoPackage, GPX, GeoParquet). Also triggers when the user wants to find places, buildings, or roads — Overture Maps provides free global data on S3 with zero API keys. Handles spatial joins, distance calculations, containment checks, density analysis, and format conversions for…
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/functions.md` and `references/overture.md`).
It sits in Backend & APIs, covering File uploads and storage and Geospatial analysis. It works with DuckDB. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 7feda8e. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
duckdbFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Spatial loads about 1k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 133 tokens; SKILL.md has 413 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from duckdb/duckdb-skills at commit 7feda8e, republished under its MIT licence (© duckdb). 413 words, ~1,026 tokens.
.claude/skills/spatial/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.You are answering spatial questions using DuckDB's spatial extension and, when needed, Overture Maps as a free global data source.
Question or file: $0
Additional context: ${1:-}
Classify the question:
| Pattern | Data source | Key functions |
|---|---|---|
| "Find X near Y" (no user file) | Overture Maps on S3 | ST_Distance_Spheroid, bbox filtering |
| "How far between A and B" | Geocode or user data | ST_Distance_Spheroid |
| "Which points fall inside polygons" | User files | ST_Contains |
| "Analyze this GeoJSON/Shapefile/GPX" | User file | ST_Read, measurement functions |
| "Show density/hotspots" | User or Overture data | H3 hex binning |
| "Convert to GeoJSON/GeoPackage" | User file | COPY TO (FORMAT GDAL) |
| "Count buildings/roads in area" | Overture Maps | bbox filtering + aggregation |
If the question involves real-world places, POIs, buildings, roads, or boundaries and the user hasn't provided a file, use Overture Maps — read references/overture.md for S3 paths and schema.
For spatial function syntax, read references/functions.md.
Always start with:
LOAD spatial;
SET geometry_always_xy = true;Add extensions as needed:
LOAD httpfs; CREATE SECRET (TYPE S3, PROVIDER config, REGION 'us-west-2');INSTALL h3 FROM community; LOAD h3;bbox filtering first — When querying Overture, always filter on bbox.xmin/xmax/ymin/ymax before any spatial function. This uses Parquet predicate pushdown and avoids downloading the full dataset.
Always set geometry_always_xy = true — This ensures all spatial functions interpret coordinates as longitude, latitude (the standard for Overture, GeoJSON, and most data sources). Without it, spheroid functions assume latitude first and return wrong results.
Use spheroid functions for real-world distances — ST_Distance_Spheroid returns meters on the WGS84 ellipsoid. Plain ST_Distance uses planar coordinates and gives meaningless results for lat/lng. Important: spheroid functions (ST_Distance_Spheroid, ST_Area_Spheroid, etc.) require POINT_2D inputs, not generic GEOMETRY. Overture geometry columns are typed GEOMETRY('OGC:CRS84') and cannot be cast directly. Extract coordinates first:
ST_Point(ST_X(geometry), ST_Y(geometry))::POINT_2DCSV with lat/lng needs conversion — ST_Point(longitude, latitude) (longitude first). This is the most common gotcha.
Run the query in a single bash call:
duckdb -c "
LOAD spatial;
<ADDITIONAL_SETUP>
<YOUR_QUERY>
"COPY TO 'result.geojson' WITH (FORMAT GDAL, DRIVER 'GeoJSON'))If the query fails:
duckdb: command not found → delegate to /duckdb-skills:install-duckdbINSTALL spatial; LOAD spatial; or INSTALL h3 FROM community; LOAD h3;© duckdb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/spatial of duckdb/duckdb-skills.
Open the folder on GitHubat commit 7feda8e
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in duckdb/duckdb-skills, which our catalogue first saw on October 7, 2026.
Spatial next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spatial this skillduckdb/duckdb-skills | 600 | 1 repos | ~1k | Automated safety check: Notes | MIT | |
| Ops Telemetry Queryboundless-xyz/boundless | 193 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Portaljs Add Geodatopian/portaljs | 2.4k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Investigate Datawalkthru-earth/geocoding-playground | 153 | — | ~935 | Automated safety check: Pass | CC-BY-4.0 | |
| Dinobase Connector Builderkappa90/dinobase | 263 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Create Environmentgodatadriven/whirl | 205 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
boundless-xyz/boundless
Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.
datopian/portaljs
Auto-ingest a geospatial file (GeoJSON, Shapefile, GeoPackage, KML/KMZ, FlatGeobuf, CSV-with-geometry) into a PortalJS portal on the user's own machine, with no server.
walkthru-earth/geocoding-playground
Investigates geocoder data quality issues by querying live S3 parquet files via MotherDuck MCP.
kappa90/dinobase
Writes a new Dinobase YAML connector for a REST API that has no verified dlt source, covering auth, pagination, read and write endpoints and incremental loading.
godatadriven/whirl
Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.
flyrank-bih/flyrank-ml-internship-starter
Works with datasets far too big to download or load in pandas — SQL over remote Parquet with DuckDB, aggregate-then-model, iterate on samples.
duckdb/duckdb-skills
Convert any data file to another format: CSV, Parquet, JSON, Excel, GeoJSON, and more.
duckdb/duckdb-skills
Explore and query data on S3, Cloudflare R2, GCS, MinIO, or any S3-compatible storage.
duckdb/duckdb-skills
Read any data file (CSV, JSON, Parquet, Avro, Excel, spatial, SQLite) or remote URL (S3, HTTPS).
duckdb/duckdb-skills
Attach a DuckDB database file for use with /duckdb-skills:query.
duckdb/duckdb-skills
Search DuckDB and DuckLake documentation and blog posts. An agent skill from duckdb/duckdb-skills.
duckdb/duckdb-skills
Run SQL queries against the attached DuckDB database or ad-hoc against files.
Works with
Categories
Answer questions about spatial data using DuckDB. An agent skill from duckdb/duckdb-skills. Spatial is an agent skill from duckdb/duckdb-skills, published by the product's own GitHub organization. Answer questions about spatial data using DuckDB.
Spatial fits situations like: the user mentions locations; geographic names; spatial file formats (GeoJSON; the user wants to find places.
Run `npx skills add duckdb/duckdb-skills --skill spatial -a claude-code`. Or copy the skill folder (skills/spatial in duckdb/duckdb-skills) into .claude/skills/spatial in your project. Claude Code loads it when a task matches its description.
Run `npx skills add duckdb/duckdb-skills --skill spatial -a codex`. Or copy the skill folder (skills/spatial in duckdb/duckdb-skills) into .agents/skills/spatial in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add duckdb/duckdb-skills --skill spatial -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spatial, .gemini/skills/spatial, .github/skills/spatial and .opencode/skills/spatial in your project.
Going by SKILL.md and its folder, Spatial needs the command-line tools its instructions call (duckdb). Its frontmatter pre-approves these tools: Bash.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Spatial is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Spatial: Ops Telemetry Query (boundless-xyz/boundless, 193 stars), Portaljs Add Geo (datopian/portaljs, 2.4k stars), Investigate Data (walkthru-earth/geocoding-playground, 153 stars) and Dinobase Connector Builder (kappa90/dinobase, 263 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
duckdb (a GitHub organization, an official publisher) maintains it in duckdb/duckdb-skills, which has 600 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on April 23, 2026.
Source: duckdb/duckdb-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.