tutorial

Build data processing pipelines using DuckDB, GDAL, and gpio as pixi tasks. Use when creating ETL workflows, multi-step data transformations, format conversions, or batch processing — even if the user just says "process this data" or "build a pipeline".

Attach a DuckDB database for persistent querying. Use when the user has a .duckdb file they want to explore, or when they want to persist query results across sessions. Explores schema and wires up state.sql so all DuckDB skills can access it.

Search DuckDB and DuckLake documentation via full-text search. Use when encountering DuckDB errors, looking up function syntax, or when other skills hit unknown DuckDB behavior. Also use proactively when unsure about DuckDB features.

Install or update DuckDB extensions. Use when DuckDB reports a missing extension, when the user asks to install/update extensions, or when other skills delegate here. Each argument is a plain extension name or name@repo. Pass --update to update.

Run SQL queries against DuckDB databases or ad-hoc files. Accepts raw SQL or natural language. Use whenever the user wants to query data, explore tables, run analytics, or ask questions about datasets — even if they don't say "DuckDB" explicitly.

Read and explore any data file (CSV, JSON, Parquet, Avro, Excel, spatial, remote) using DuckDB. Use proactively when the user mentions a data file, asks "what's in this file", or wants to explore/preview/describe any dataset — even without saying DuckDB.

Search past Claude Code session logs to recover context. Use proactively when recalling past decisions, patterns, or unresolved work from previous sessions.

Initialize and manage shared DuckDB session state (state.sql). Use when setting up extensions, credentials, or macros that all DuckDB skills share. Other skills delegate here for session initialization.

Validate project environment health. Use before running pipelines, after setup, or when tools fail unexpectedly. Checks pixi, DuckDB, GDAL, gpio, extensions, state.sql, and cross-tool compatibility.

Geospatial data processing with the unified GDAL CLI (3.12+). Use when converting, inspecting, reprojecting, or processing raster/vector data — even if the user just says "convert this shapefile" or "what CRS is this file". Replaces legacy ogr2ogr/gdalinfo/ogrinfo.

GeoParquet optimization via gpio CLI (geoparquet-io). Use when creating, inspecting, validating, sorting, partitioning, or enriching GeoParquet files — even if the user just says "optimize this parquet" or "add spatial index". Covers Hilbert sorting, compression, bbox covering, STAC metadata, and cloud upload.

Browser automation with Playwright. Use when testing websites, taking screenshots, checking responsive design, filling forms, testing login flows, checking links, or any browser-based task. Auto-detects dev servers and writes scripts to .tmp/.

Geospatial analysis with DuckDB spatial (155+ ST_* functions) and unified GDAL CLI. Use when the user asks about spatial queries, geometry ops, coordinate transforms, distance/area calculations, spatial joins, or any map data processing.