postgis-skill

Write and document geospatial SQL queries for PostGIS.

Updated Dec 13, 2025

Search Tags:#documentation #SQL #geometry #best-practices #geospatial #PostGIS

Ready to run

npx skills add https://github.com/frenata/postgis --skill postgis-skill-frenata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postgis-skill
Source: https://github.com/frenata/postgis/tree/main/doc
Command: npx skills add https://github.com/frenata/postgis --skill postgis-skill-frenata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostGIS SQL tips and gotchas help developers write robust, readable geospatial SQL for PostgreSQL with PostGIS.

Core Features & Use Cases

Documentation-oriented: establishes guidelines for commenting and documenting SQL statements that operate on geometries.
Best practices: covers naming conventions, consistent casing, and safe patterns for common PostGIS operations.
Use case: when refactoring a complex query using ST_ functions, this skill provides checklists to ensure correctness and maintainability.

Quick Start

Run a quick review of a sample geospatial query and apply the tips to produce a cleaner, better-documented version.

Frequently Asked Questions about postgis-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are common gotchas when writing geospatial SQL queries with PostGIS?▼

Common PostGIS gotchas include mishandling geometry types, inconsistent casing in ST_ functions, and neglecting to document spatial relationships clearly, which this skill helps you avoid.

How do I document and refactor complex PostGIS SQL queries?▼

You can refactor complex PostGIS queries by applying established naming conventions, consistent casing, and documentation checklists to ensure your ST_ functions remain correct and maintainable.

What are the best practices for naming conventions in PostGIS SQL?▼

PostGIS best practices for naming involve using consistent casing for ST_ functions and establishing clear guidelines for commenting on geometry operations to improve query readability.

Does this skill help debug ST_ functions across different geometry types?▼

Yes, it provides operational guidance for debugging and writing PostGIS queries across various geometry types, ensuring your spatial SQL operates safely and correctly.

When should I apply a checklist to my PostGIS SQL statements?▼

You should apply a checklist when refactoring complex geospatial queries to verify that all ST_ functions operate on the correct geometry types and maintain query correctness.