Evidence record · captured 2026-10-11

Postgres Best Practices

A Postgres rulebook maintained by Supabase that the agent loads before changing anything in a database: rules across 8 impact-ranked categories (query performance and indexing, connection management and pooling, schema design and column types, RLS policies and their tests, migrations, batch inserts and N+1, JSONB and full-text search). Each rule has incorrect vs correct SQL and query-plan reasoning.

Community publisherUnverifiedSource reviewedBehavior not tested

Source review

Editorial assessment

This is a source-only assessment. It does not claim runtime or security testing.

What it does

A library of short Postgres rules, each with incorrect and correct SQL, that the agent is told to load before any database change, even a one-column edit. It targets Postgres anywhere, with Supabase notes where relevant.

Best for

Adding indexes, constraints or columns and wanting the agent to check common mistakes first
Writing row level security policies for multi-tenant tables
Diagnosing slow queries, connection exhaustion or lock contention

Strengths in the source

About 30 rule files across 8 impact-ranked categories (query, connections, security and RLS, schema, locking, data access, monitoring, advanced), each with incorrect and correct SQL.
Rules address real migration traps, such as Postgres having no ADD CONSTRAINT IF NOT EXISTS, with an idempotent DO-block pattern instead.
Covers RLS beyond enabling it: FORCE ROW LEVEL SECURITY for table owners and policy performance, including SECURITY DEFINER usage.

Limitations

The description promises guidance on pgvector, pg_cron, pgmq, pg_restore, declarative schema files and RLS tests, but no reference file at this commit covers those topics.
Several examples use Supabase constructs such as auth.uid() and the authenticated role, which need translating for plain Postgres.
Rules are brief and generic, so they inform decisions but do not inspect your actual schema or query plans.

When not to use it

Databases other than Postgres, including MySQL and SQLite-based stores
Platform-specific operations such as branching, pooling endpoints or restores, which belong to the host's own guidance

Reviewed by Retenta editorial on 2026-10-11; scope: source only.

Files included in this review

skills/supabase-postgres-best-practices/SKILL.md

Evidence and boundaries

Execution · not tested

Retenta has not executed this skill.

Security · not tested

The skill folder bundles no executable scripts. Retenta has not run a security scan.

Pinned publisher source: skills/supabase-postgres-best-practices/SKILL.md
Revision: c9be0e931b7930f7d02126d04774d904c381e7d7
License evidence: MITRetenta preserves the license text captured with this immutable upstream snapshot; no independent legal or security review is claimed.
Last source change: 2026-07-30
Independent verification: Published by Supabase, which does not own the product this skill covers. Not independently verified.
Upstream repository: Open publisher repository