Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
65
48%
Does it follow best practices?
Impact
92%
1.27xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/database-design/skills/postgresql/SKILL.mdCore data types and FK indexing
BIGINT IDENTITY PK
0%
83%
No SERIAL type
0%
100%
NUMERIC for price/money
100%
100%
No money type
100%
100%
TIMESTAMPTZ for timestamps
100%
100%
No plain TIMESTAMP
100%
100%
TEXT not VARCHAR
0%
100%
No VARCHAR/CHAR
0%
100%
FK indexes present
100%
100%
snake_case naming
100%
100%
NOT NULL on required fields
100%
100%
Status as TEXT + CHECK
0%
50%
Full-text search and JSONB design
TSVECTOR column
100%
100%
GIN index on tsvector
100%
100%
Language in to_tsvector
100%
100%
Language in to_tsquery
100%
100%
JSONB not JSON
100%
100%
GIN index on JSONB
0%
100%
TIMESTAMPTZ not TIMESTAMP
100%
100%
BIGINT IDENTITY PK
0%
100%
No SERIAL type
0%
100%
BRIN or RANGE partition for dates
100%
0%
UNLOGGED staging table
100%
100%
Range types, exclusion constraints, update-heavy design
tstzrange for time slots
100%
100%
GiST index on range
100%
100%
EXCLUDE for double-booking
100%
100%
Array + GIN for tags
100%
100%
Junction table for teams
100%
100%
fillfactor on reservations
100%
100%
Hot/cold column separation
100%
100%
ENUM for stable values
100%
0%
TEXT+CHECK for reservation status
0%
100%
BIGINT IDENTITY PKs
0%
100%
FK indexes present
100%
100%
47823e3
Table of Contents
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.