Agent Plugins Marketplace
← All plugins

geospatial-engineering

v0.2.2

Geospatial / GIS engineering team — agents. The geospatial-data-engineer owns spatial data modeling and storage (PostGIS, GiST/SP-GiST indexes, SRID/projection hygiene — EPSG:4326 vs 3857, geometry vs geography), spatial SQL and analysis (ST_ functions, joins, nearest-neighbor, buffers), spatial data quality (validity, validate-at-load), and pipelines (GDAL/OGR, geocoding, routing like OSRM/Valhalla). The mapping-visualization-engineer owns serving and visualization (vector tiles/MVT, pg_tileserv/Martin/Tegola, MapLibre/Mapbox GL styling, the GeoJSON-vs-vector-tile tradeoff). skills, projection + storage/serving decision trees, a dated 2026 stack reference, templates, best-practices, an advisory hook (checks). Seams: warehouse/ELT → data-platform; OLTP → database-engineering; map UI → frontend-engineering. Requires ravenclaude-core@>=0.7.0.

Claude Code4 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
4 skill or MCP entries
Source updated
Sep 15, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install geospatial-engineering for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install geospatial-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/geospatial-engineering/.

Plugin files

plugins/geospatial-engineering/
├── .claude-plugin/plugin.json
├── skills/design-postgis-schema/SKILL.md
├── skills/serve-vector-tiles/SKILL.md
├── skills/spatial-data-quality/SKILL.md
└── skills/write-spatial-query/SKILL.md

Included Skills4

design-postgis-schemaskills/design-postgis-schema/SKILL.md

Design a PostGIS table for spatial data — pick the CRS (SRID) and geometry-vs-geography type by use-case, declare the column with an explicit SRID, add the right GiST/SP-GiST spatial index, and emit a runnable CREATE TABLE + index. Reach for this when the user wants to store points/lines/polygons in PostGIS and asks "which SRID?" or "geometry or geography?". Used by `geospatial-data-engineer` (primary).

serve-vector-tilesskills/serve-vector-tiles/SKILL.md

Serve geospatial data to a web map — decide GeoJSON vs vector tiles (MVT) by feature count and zoom, stand up a tile server (pg_tileserv / Martin / Tegola or MBTiles), and wire the MapLibre source + layer to consume it. Reach for this when a map is slow, you have many features, or you need a tile-serving architecture. Used by `mapping-visualization-engineer` (primary).

spatial-data-qualityskills/spatial-data-quality/SKILL.md

Keep spatial data trustworthy: geometry validity (ST_IsValid / ST_MakeValid, self-intersections, ring order), topology, declared-vs-actual SRID checks, coordinate-order (lon/lat) sanity, and validating geometry at load time so bad data never lands. Reach for this when loading a dataset, debugging a function that crashes on some rows, or hardening an ingest. Used by `geospatial-data-engineer` (primary).

write-spatial-queryskills/write-spatial-query/SKILL.md

Write or fix a spatial SQL query in PostGIS — spatial joins, nearest-neighbor (KNN), buffers, ST_DWithin proximity — so it uses the GiST index and returns sensible units. Reach for this when a query is slow, returns degrees, or you need an index-aware ST_ query. Diagnoses the common smells (no index, degrees-not-metres, SRID mismatch). Used by `geospatial-data-engineer` (primary).

Plugin manifests1

plugins/geospatial-engineering/.claude-plugin/plugin.json
{
  "name": "geospatial-engineering",
  "version": "0.2.2",
  "description": "Geospatial / GIS engineering team — agents. The geospatial-data-engineer owns spatial data modeling and storage (PostGIS, GiST/SP-GiST indexes, SRID/projection hygiene — EPSG:4326 vs 3857, geometry vs geography), spatial SQL and analysis (ST_ functions, joins, nearest-neighbor, buffers), spatial data quality (validity, validate-at-load), and pipelines (GDAL/OGR, geocoding, routing like OSRM/Valhalla). The mapping-visualization-engineer owns serving and visualization (vector tiles/MVT, pg_tileserv/Martin/Tegola, MapLibre/Mapbox GL styling, the GeoJSON-vs-vector-tile tradeoff). skills, projection + storage/serving decision trees, a dated 2026 stack reference, templates, best-practices, an advisory hook (checks). Seams: warehouse/ELT → data-platform; OLTP → database-engineering; map UI → frontend-engineering. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "geospatial",
    "gis",
    "postgis",
    "spatial-sql",
    "vector-tiles",
    "maplibre",
    "gdal",
    "srid",
    "projections",
    "geocoding",
    "routing",
    "mvt"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[geospatial-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/geospatial-engineering)