What problem does it solve? Supabase features, CLI commands, and API conventions change frequently, so relying on stale training data leads to broken implementations and silent security vulnerabilities like misconfigured RLS policies or exposed service keys. This Skill keeps Supabase work grounded in current documentation and enforces a security checklist for auth, RLS, views, and storage. ## Core Features & Use Cases - Security Checklist Enforcement: Catches Supabase-specific traps such as views bypassing RLS, SECURITY DEFINER functions exposed in public schemas, deprecated auth.role() usage, and BOLA/IDOR policy gaps. - Schema Change Workflow: Directs safe iteration with execute_sql or supabase db query, then commits changes via advisors, db pull, and migration verification. - CLI and MCP Troubleshooting: Provides version-aware CLI guidance, known gotchas, and step-by-step MCP server connection diagnostics. - Use Case: When adding a new orders table with row-level security in a Next.js app, the Skill ensures RLS is enabled, policies use TO authenticated with ownership predicates, and the migration is generated and verified correctly. ## Quick Start Ask the agent to create a new Supabase table with RLS policies and generate a verified migration for it.