geospatial-marketplace

This skill should be used when the user asks to "convert this shapefile to SQL", "show me the MongoDB inserts for this geodatabase", "give me the PostGIS DDL for this DWG", "translate this GIS file to JSON I can paste into Mongo", or invokes `/gis-to-db:convert <file>`. Parses a GIS or CAD file inline using fiona/ezdxf/LibreDWG (host or Docker), then prints ready-to-execute SQL inserts (PostGIS or MySQL spatial) or MongoDB documents directly into the chat. Does NOT write to a database — the user can copy the output, review, and run themselves.

This skill should be used when the user asks to "publish the cadastre", "generate a public-facing parcel map", "create a parcel lookup API", "produce official extract PDF", "publish land registry to the web", "generate cadastre change log", "public cadastre publication", or invokes `/civic-gis:cadastral-publish`. Takes an official cadastral dataset (typically the output of `gis-to-db:convert` to PostGIS or MongoDB) and produces public-facing artifacts: a searchable Leaflet map, parcel-extract PDF templates, JSON API stubs, and a change log against the previous publication.

This skill should be used when the user discusses municipal or civic GIS work — terms like "zoning ordinance", "setback", "FAR (floor area ratio)", "lot coverage", "building permit", "use permit", "variance", "rezoning", "master plan", "cadastre", "parcel ID", "deed", "title", "land registry", "PIN" (Parcel Identification Number), "tax map", "ROW (right of way)", "easement", "land-use code", "comprehensive plan", "subdivision", "plat", "TIF (tax increment financing)", "opportunity zone", "enterprise zone", "investment incentive", "economic development", "investor profile", "site selection", "small town economic development", "post-conflict reconstruction", "damage assessment", "displaced persons", "property restitution", or asks about civic / municipal / governmental geospatial workflows in any country (US, Europe, MENA, etc.). Provides terminology, data-source references, ruleset patterns, and cross-jurisdiction guidance.

This skill should be used when the user asks to "generate an investor profile for this town", "create an economic development pitch", "show investor metrics for city X", "what would investors want to know about this town", "build an investment one-pager", "town profile for site selection", "economic development brief", or invokes `/civic-gis:investment-profile`. Generates an investor-ready profile of a small city or town: demographics, infrastructure, available land, key industries, incentives, comparable cities. Pulls from user-supplied data and free public sources. Outputs markdown, JSON, or a one-page PDF brief.

This skill should be used when the user asks to "find suitable sites for this investment", "match a proposed investment to parcels", "where could this factory go in this town", "show me parcels matching these criteria", "site selection for X industry", "investment site matching", or invokes `/civic-gis:investment-sites`. Filters a town's parcel inventory against an investment brief (industry, size, budget, requirements) and returns ranked candidate sites with concrete rationale. Composes on top of gis-to-db's analyze-site rule engine.

This skill should be used when the user asks to "monitor land use changes", "detect unauthorized changes in land use", "compare current land use against the master plan", "land use change detection", "flag illegal conversions", "track parcel use over time", "land use compliance monitoring", or invokes `/civic-gis:landuse-monitor`. Periodically compares the current land-use snapshot against an approved master plan AND against the previous snapshot, flags both unauthorized changes (current ≠ master plan) and recent changes (current ≠ previous snapshot). Composes on top of gis-to-db:analyze-diff.

This skill should be used when the user asks to "check if this project complies with zoning", "validate a building permit application", "does this proposal meet setback requirements", "check zoning rules for site X", "permit compliance check", "is this project allowed in zone Y", or invokes `/civic-gis:permit-check`. Scores a proposed project (location + building parameters) against a jurisdiction's zoning ruleset and reports violations with citations. Rule-based and transparent — produces a per-rule pass/fail report, never a black-box decision.

This skill should be used when the user asks to "track reconstruction progress", "compare pre-conflict vs current cadastre", "damage assessment for this area", "find destroyed buildings", "post-conflict reconstruction monitoring", "map damaged parcels", "show reconstruction status", or invokes `/civic-gis:reconstruction-tracker`. Compares a pre-event cadastre baseline (parcels + buildings before conflict / disaster) with a post-event survey or remote-sensing layer, classifies each parcel as intact / damaged / destroyed / rebuilt, and produces a per-parcel status report plus aggregate statistics. Composes on top of gis-to-db:analyze-diff.

This skill should be used when the user asks to "add a GIS ingestion feature to my app", "scaffold a DWG upload feature into my NestJS / FastAPI / Django / Angular / React / Next.js / Vue project", "wire shapefile parsing into my existing application", "add a geospatial module to this codebase", or invokes `/gis-to-db:add-module`. Detects the host application stack from manifests (`package.json`, `pyproject.toml`, `angular.json`, `next.config.js`), then scaffolds a complete GIS ingestion feature: a Python FastAPI sidecar service for parsing + a host-language backend module (NestJS / FastAPI / Django) + a frontend component (Angular / React / Next.js / Vue) + docker-compose wiring + tests. The sidecar handles all GIS parsing; the host app stays in its native language.

This skill should be used when the user asks to "compare these two GIS datasets", "what changed between this cadastre version and that one", "diff these shapefiles", "find added or removed parcels", "before and after comparison", "what features moved", or invokes `/gis-to-db:analyze-diff`. Compares two GIS layers — typically two versions of the same dataset over time — and reports added features, removed features, geometry changes (movement, area drift), and attribute changes per feature. Matches features by an attribute key (e.g. `parcel_id`) or by geometric proximity when no key is supplied.

This skill should be used when the user asks to "find clusters in this data", "are these points clustered or random", "show me hot spots", "kernel density of features", "spatial clustering with DBSCAN", "find areas with high point density", "nearest neighbor analysis", "spatial pattern detection", or invokes `/gis-to-db:analyze-patterns`. Runs spatial pattern analysis on a GIS point layer: DBSCAN clustering, nearest-neighbor distance distribution, kernel density estimation summary, and convex hulls of detected clusters. Returns labeled features (which cluster each point belongs to) plus a summary report.

This skill should be used when the user asks to "evaluate this location", "is this a good site for X", "site suitability analysis", "why is this location good/bad for an airport / hospital / residential development / factory / solar farm", "score this candidate site", "compare two locations for purpose Y", "site selection criteria", or invokes `/gis-to-db:analyze-site`. The skill scores a candidate point or polygon against a per-purpose ruleset (terrain slope, distance to roads/cities/water, conflict with protected zones, flood risk, demographic context) and produces a transparent markdown report with weighted criteria, scores, and concrete "why" sentences. Rule-based, explainable — no ML, no training data needed.

This skill should be used when the user asks to "show statistics for this GIS layer", "describe the attribute distributions", "summarize this shapefile", "what's the geometry validity of this dataset", "how many duplicates are in this layer", "histogram of parcel areas", "outliers in this data", "data quality report", or invokes `/gis-to-db:analyze-stats`. Produces descriptive statistics for a GIS layer: attribute distributions (numeric histograms, categorical counts), geometry validity report (invalid / self-intersecting / empty), duplicates by attribute or geometry, area / length distributions, feature count breakdown. Pure read-only analysis on a single layer.

This skill should be used when the user mentions GIS or CAD file formats ("Shapefile", "GeoJSON", ".gdb", "File Geodatabase", "DWG", "DXF", "KML"), geospatial actions ("convert GIS file", "import shapefile", "ingest geometry", "load spatial data"), CRS or projection topics ("EPSG", "SRID", "WGS84", "reproject", "UTM zone", "coordinate system"), DB-specific spatial features ("PostGIS", "ST_GeomFromGeoJSON", "geometry vs geography", "2dsphere index", "MongoDB GeoJSON", "MySQL spatial", "GIST index"), GDAL tooling ("fiona", "geopandas", "ogr2ogr", "ezdxf", "LibreDWG"), or domain-specific geometry work ("parcel boundaries", "cadastral data", "site plan", "building footprint", "zoning", "pipeline route", "flood zone", "topographic", "land registry").

This skill should be used when the user asks to "inspect", "describe", "preview", "analyze", or "look inside" a GIS or CAD file (`.shp`, `.gdb`, `.dwg`, `.dxf`, `.geojson`, `.kml`), or asks "what's in this shapefile / geodatabase / DWG", "show me the layers", "what CRS does this use", "how many features", "list the attributes". Invoked as `/gis-to-db:inspect <file> [--json] [--features-sample N]`. Read-only — never writes to the user's filesystem outside `/tmp` and never touches a database.

This skill should be used when the user asks to "create a CLI for GIS ingestion", "generate a one-shot script to import shapefiles", "make a command-line tool that loads DWG files into PostGIS", "write a Python CLI for geodatabase to MongoDB", or invokes `/gis-to-db:make-cli`. Produces a standalone Python CLI built with Typer + geopandas/fiona/ezdxf that takes a GIS or CAD file plus a DB URI and ingests features in one command. Lighter than scaffold-service — no FastAPI, no async jobs, no Docker compose — designed for ad-hoc per-file ingestion runs.

This skill should be used when the user asks to "scaffold a GIS ingestion service", "create a GIS upload API", "build a FastAPI service for shapefile/DWG/.gdb ingestion", "generate a geospatial ingestion microservice", or invokes `/gis-to-db:scaffold-service`. Produces a complete, production-grade FastAPI service that accepts GIS/CAD file uploads, parses them via fiona/ezdxf/LibreDWG, reprojects to a target SRID, and writes geometries to PostGIS, MongoDB, or MySQL spatial. Includes API key auth, Pytest tests, Arq async job queue, Prometheus metrics, structured logging, and Docker compose wiring.