Supabase Skills Eval Scenarios

#	Scenario	Description
1	auth-rls-new-project	Initialize a Supabase project and create a tasks table with RLS
2	team-rls-security-definer	Team-based RLS with security definer helper in a private schema
3	storage-rls-user-folders	Storage buckets with RLS policies for user-isolated folders
4	edge-function-hello-world	Hello-world Edge Function with CORS and shared utilities
5	collaborative-rooms-realtime	Collaborative rooms with role-based RLS, broadcast triggers, and Realtime authorization
6	auth-fk-cascade-delete	Profiles table with auth.users FK cascade and auto-create trigger
7	rls-update-needs-select	Orders table where UPDATE silently fails without a matching SELECT policy
8	extension-wrong-schema	pgvector extension setup with correct schema placement, HNSW index, and user-scoped RLS
9	connection-pooling-prisma	Fix Prisma schema to use Supabase transaction-mode pooler (port 6543, pgbouncer=true, directUrl) for serverless deployments
10	cli-hallucinated-commands	CLI cheat-sheet that must use only real Supabase CLI commands, avoiding hallucinated `supabase functions log` and `supabase db query`
11	postgrest-schema-cache	Add columns and a view to an existing table, with NOTIFY pgrst to reload the PostgREST schema cache
12	rls-user-metadata-role-check	Documents table with owner and admin RLS — must use app_metadata not user_metadata for role authorization
13	service-role-edge-function	Admin Edge Function that bypasses RLS using the service role key via env vars, never hardcoded