walkthru-earth

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.

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.

DuckDB v1.5 spatial/GIS analytics with ST_*, H3, A5, and S2/geography extensions. Use for SQL queries, file exploration, spatial analysis, discrete global grids, GeoParquet, ArcGIS REST, DuckLake, session state, docs search, or extension management, even without saying "DuckDB".

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".

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.

Investigates geocoder data quality issues by querying live S3 parquet files via MotherDuck MCP. Use this skill when the user reports a bug in autocomplete results, duplicate entries, missing data, wrong city/street/postcode results, or asks to check data for a specific country. Also use when the user says 'check the data', 'investigate', 'query S3', 'what does the index look like', 'how many streets/cities/postcodes', or 'verify the data'. Do NOT use for frontend UI bugs, build issues, or code refactoring.

Tests the smart autocomplete engine against known test scenarios from the study docs. Use this skill when the user asks to 'test autocomplete', 'verify search works', 'check the parser', 'test address parsing', 'run autocomplete tests', or wants to validate that a specific country's input classification and ranking works correctly. Also use after making changes to autocomplete.ts, address-parser.ts, or search.ts. Do NOT use for data investigation (use investigate-data instead) or UI testing.