Skill profile
supabase-postgres-best-practices
Postgres performance-optimization guidelines from Supabase, covering query performance, connection management, schema design, RLS, and monitoring — prioritized by impact.
What it actually does
- Postgres performance-optimization guidance across eight categories, each prioritized by impact: query performance and RLS (critical), connection management (critical), schema design (high), concurrency/locking (medium-high), data access patterns (medium), and monitoring (low-medium).
When to use it — and when not to
Use it when
- Writing SQL, designing a schema, reviewing a performance problem, configuring connection pooling, or working with Row-Level Security.
Not for
- General Supabase platform work outside Postgres performance — the broader `supabase` skill covers that.
Agent compatibility
- Claude Code
- Cursor
Same compatibility statement as the general supabase skill — named explicitly among Supabase's 18+ supported agents.
Confirmed means the skill’s own source or vendor states it works with that agent. Portable means it only reaches that agent through the shared SKILL.md format and a directory convention — real, but a weaker claim. An agent with no entry here isn’t known to be unsupported; it simply isn’t documented either way, so nothing is claimed. Full model on Agent Skills Compatibility.
Requirements and operational surface
Depends on
- A Postgres or Supabase database to apply the guidance to
Related skills
- supabaseSame source repository — the general platform skill this one narrows down from.
Evidence and provenance
Maintained by Supabase (vendor). Primary source: supabase/agent-skills, last checked against this page’s claims on . This page summarizes and analyzes that source — it isn’t a copy of its SKILL.md or README, and installation happens at the source, not here.