Supabase Postgres Best Practices Skill

Publisher: Supabase plugin in openai/plugins · Editorial profile by AI Tools Ratings · Review method

What task is this skill designed for?

Start with a specific slow query or schema change. Compare a proposed optimization against realistic row counts and query plans rather than treating a generic index rule as universal.

What input and output should you expect?

Input: Sanitized SQL, table definitions, index definitions, estimated row counts and an explain plan. Include write frequency and access rules so read speed is not optimized at their expense.

Output: A prioritized review with suggested SQL changes, expected tradeoffs and a reproducible before-and-after measurement plan.

What does it need to run?

A coding agent and the full references folder. Database access is optional for source review; actual measurements require an isolated database with representative test data.

Published in the OpenAI Codex plugins repository. Compatibility evidence is the plugin package and its source instructions; this is not a claim of identical behavior in other agent clients.

How should you approach installation?

1. Open the pinned source and review the complete skill folder, including referenced helpers and license, before enabling it.
2. Use the corresponding plugin in a compatible Codex environment; preserve the skill folder structure rather than copying only SKILL.md. Confirm current plugin availability in your client.
3. Start with a disposable project and the trial prompt below. Grant only the stated access, inspect the proposed diff, and require separate approval for remote writes or publishing.

Installation guide: discovery, dependencies and runtime checks

What files, accounts or data can it access?

Files can be read or edited. If database tools are enabled, queries may expose rows or mutate schemas; use a read-only connection first and approve migrations separately.

What does the skill cost?

Guidance has no per-query skill charge. Database compute, storage, test environments and coding-agent usage remain separate; benchmark plans should include cleanup.

What are its limits and alternatives?

Example metrics are not results for your database. Extra indexes affect writes and storage, and query-plan improvements can vary with parameters or statistics.

Use the general Supabase skill for auth, storage and platform integration; ask a database specialist for high-risk production migrations.

What could you ask in a small trial?

Try this with a small sample:

Review this slow lookup using only the supplied schema and explain plan. Propose one change, explain its write cost and supply a staging comparison plan. Do not run migrations or query production.

How would you verify the result?

1. The recommendation matches the actual predicate and sort order.
2. Before-and-after plans use comparable data and parameters.
3. Write overhead and index storage are considered.
4. Row-level access behavior is unchanged by the proposed optimization.

Use a baseline and record acceptance evidence before treating a successful task as a reliable workflow.

Which source and license were checked?

Read the reviewed SKILL.md at its pinned commit · Complete reviewed folder

Repository and current publisher guidance

Checked: 2026-10-30

MIT License evidence

Report an error, license concern or request a new review.