Spatial Sql

Community

jaakla

spatial-sql

Write, review, debug or optimize spatial SQL on an already chosen engine, including DuckDB Spatial, PostGIS, BigQuery GIS, Snowflake and Sedona. Use for spatial predicates, joins, indexes, query plans, CRS and metric/geodesic correctness. Route unresolved engine or cross-system architecture choices to open-map-stack; ordinary non-spatial SQL and casual place questions are outside this skill.

Overview

Publisher	jaakla
Repository	`openmapstack-skills`
Skill name	`spatial-sql`
Stars	77
Forks	11
Bundled files	5
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
5 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jaakla on GitHub. Read the source before you install it.

Installation

Install the Spatial Sql AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jaakla/openmapstack-skills/tree/main/skills/spatial-sql
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jaakla/openmapstack-skills.git /tmp/openmapstack-skills
mkdir -p .claude/skills
cp -r /tmp/openmapstack-skills/skills/spatial-sql .claude/skills/spatial-sql

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Spatial Sql in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Spatial Sql on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Spatial Sql is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Spatial SQL

Solve the query in the engine the user has chosen. Read references/spatial-sql.md for the relevant engine and query patterns, and references/formats-and-crs.md when coordinate or format semantics matter.

When the user has dlt, Dagster, dbt, QGIS or Observable in their stack, read references/established-stack.md for ownership and integration boundaries. Preserve their chosen tools; retain source pins, GIS correctness and reproducible evidence. Do not duplicate their SQL, ingestion or scheduler definitions.

Query workflow

Establish the engine/version, available spatial functions, geometry versus geography types, CRS/SRID, input grain, expected result and scale. Inspect the existing query and plan when available. Do not assume different engines share function signatures, boundary semantics or index behavior.
Express the intended spatial relationship precisely. Resolve intersects versus contains/covers, boundary inclusion, null/empty/invalid geometries, and whether several spatial matches should duplicate an entity or produce a single membership result.
Make distance, area and buffers use the intended units and method. A geographic geometry in EPSG:4326 does not acquire metre units from a numeric threshold. Use the engine's explicitly supported geodesic/geography operation, or a projected CRS whose area of use contains the data's known extent. For distance and within-distance tests on an unknown or wide extent, prefer an operation the engine documents as geodesic for the geometry types involved; do not guess a UTM zone or national grid. A geography type does not make every operation geodesic: check buffers and other constructions per operation. Assigning an SRID is not coordinate transformation; Web Mercator is not a general metric-analysis CRS.
Preserve analytical correctness while improving execution. Consider spatial indexes or candidate filters, predicate pushdown, partition pruning and join cardinality. An expression or cast can prevent use of an existing index; verify the relevant plan instead of promising index use by syntax.
Run a small meaningful control when an engine is available: qualifying and non-qualifying features, a boundary, and duplicate matches where relevant. Report actual execution evidence separately from a reasoned SQL review. An unavailable engine is not_testable, not a successful query run.

Return corrected SQL, consequential assumptions and a short explanation of correctness and performance. Do not create a full GIS project for a bounded query review. Preserve source data; an optimization must not silently change the metric, feature population or authoritative geometry.

When the task expands

Engine selection, shared-system design and joint compute/storage/delivery trade-offs belong with an installed open-map-stack or an explicit architecture discussion. Compiling a material analysis belongs with the generalist or reproducible-gis-project. Keep the SQL contribution bounded and supply the assumptions/evidence needed for that handoff; do not claim to have completed the whole analysis.

No project template, worked example or OpenMapStack CLI is needed for a bounded query task. Hand off the SQL and its assumptions to an installed open-map-stack or reproducible-gis-project if the user also wants a full project. Sibling skills are optional and are never automatically installed.

For optional product expertise, read references/companion-skills.md. Keep GIS correctness and the task boundaries above when using a companion.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Spatial Sql AI skill do?

Why use Spatial Sql on TypingMind?

Because you install it once and use it with any model. Spatial Sql is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Spatial Sql in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jaakla/openmapstack-skills/tree/main/skills/spatial-sql. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Spatial Sql?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Spatial Sql?

As many as you like. As long as a model supports skills, you can use Spatial Sql with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Spatial Sql AI skill free?

Yes. It is published on GitHub by jaakla under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gstack Openclaw Ceo Review

garrytan

CommunityPopular

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

Caveman Stats

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Notcrawl

Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Spatial SQL

Query workflow

When the task expands

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now