design-postgis-tables

Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/design-postgis-tables/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with executable SQL and strong technical depth, but it is a long monolithic reference that could be split into referenced files and tightened to reduce redundancy. Workflow guidance lacks explicit validation checkpoints.

Suggestions

Split the type catalog, SRID reference, and performance patterns into separate referenced files (e.g. GEOMETRY_TYPES.md, SRIDS.md) and keep SKILL.md as an overview with one-level-deep pointers.

Consolidate the overlapping POI/parcels/GPS/service-zone examples into fewer canonical patterns or move variants to an examples file to cut redundancy.

Add an explicit design-decision checklist with validation checkpoints (e.g. verify SRID consistency, confirm index usage with EXPLAIN ANALYZE) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is a dense technical reference that mostly avoids explaining basics Claude already knows, but at ~495 lines it repeats overlapping patterns across the POI, parcels, GPS, and service-zone examples and could be tightened, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready SQL — CREATE TABLE statements with constraint-based typing, GiST/BRIN/SP-GiST indexes, and concrete query patterns — matching the 'fully executable code, copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 'Before You Start (5 Questions)' section gives a loose design sequence, but there are no explicit validation checkpoints or feedback loops for the design process, matching the 'steps present but checkpoints missing or implicit' anchor; it is not a simple single-action skill that could auto-score 3.	2 / 3
Progressive Disclosure	There are no bundle files and the entire ~495-line reference is inline; section organization is good (not a monolithic wall), but material that could be split out (type catalog, SRID tables, performance patterns) is inline, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

72%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-differentiated with strong trigger terms, but it omits an explicit 'when to use' clause, capping its completeness. Adding a 'Use when…' sentence would raise it to a top score.

Suggestions

Add an explicit 'Use when…' clause naming trigger situations, e.g. 'Use when designing PostGIS-backed tables, choosing geometry vs geography, or setting up spatial indexes for location-based apps.'

Reframe some noun phrases as concrete actions (e.g. 'design', 'index', 'validate') to lift specificity from a coverage list to an action list.

Dimension	Reasoning	Score
Specificity	The description names the domain and several sub-topics ('geometry types, coordinate systems, spatial indexing, and performance patterns') but frames them as nouns under 'reference covering' rather than listing concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It clearly answers 'what' the reference covers but provides no 'Use when…' or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	It surfaces natural terms a user would say when needing this skill — 'PostGIS', 'spatial', 'geometry types', 'spatial indexing', 'location-based applications' — giving good coverage of likely trigger language.	3 / 3
Distinctiveness Conflict Risk	'PostGIS spatial table design' is a clearly delineated niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: timescale/pg-aiguide
Path: skills/design-postgis-tables/SKILL.md
Commit: b4f11a4

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.