Postgis Query Patterns
Use when writing PostGIS or spatial SQL — distance, proximity, intersection, or geometry storage queries. Makes the agent use correct SRIDs, spatial indexes, and the right ST_ functions, so spatial SQL is both correct and fast instead of silently slow or wrong.
Install
$ agentstack add skill-buildmoonshot-skillpacks-postgis-query-patterns ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-buildmoonshot-skillpacks-postgis-query-patterns) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
PostGIS Query Patterns
PostGIS rewards correct spatial SQL and quietly punishes the rest with wrong answers or full table scans. Follow the patterns.
Storage & SRID
- Store geometry with a known SRID (typmod like
geometry(Point, 4326)orST_SetSRID). Operations between different SRIDs error or mislead —ST_Transformto align. - Choose
geographyfor accurate distances over large/global areas (meters on a sphere);geometryin an appropriate projected CRS for fast planar math.
Make queries use the index
- Put a GiST index on every geometry column you query.
- Use index-assisted operators/functions:
&&,ST_Intersects,ST_DWithin. These hit the index. - Avoid
ST_Distance(a, b) < xin a WHERE clause — it can't use the index and forces a full scan. UseST_DWithin(a, b, x)instead.
Correctness gotchas
&&is bounding-box only — fast but approximate. Use it as a prefilter, thenST_Intersectsfor the exact test.- Validate geometry before overlays (
ST_IsValid/ST_MakeValid) — seevalidate-geometry. ST_DWithindistance units follow the type: meters forgeography, CRS units forgeometry(degrees if you left it in 4326 — usually not what you want for a distance).
Why this matters
Spatial SQL fails quietly in two directions: wrong SRID or wrong function gives a confident wrong answer, and a missing index turns a sub-second query into a minutes-long table scan that still "works" in testing and falls over in production. The patterns above keep queries both correct and fast.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: buildmoonshot
- Source: buildmoonshot/skillpacks
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.