supabase

Guides Supabase development tasks including schema changes, RLS policies, auth, and CLI workflows.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/nimdvir/dima-publishing --skill supabase-nimdvir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/nimdvir/dima-publishing/tree/main/.continue/skills/supabase
Command: npx skills add https://github.com/nimdvir/dima-publishing --skill supabase-nimdvir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Supabase evolves quickly, and outdated training data leads to broken implementations, insecure RLS policies, and subtle auth vulnerabilities. This Skill keeps AI agents aligned with current Supabase documentation, changelogs, and security best practices when building or debugging Supabase projects. ## Core Features & Use Cases - Security checklist enforcement: Catches Supabase-specific traps like user_metadata in JWT authorization, views bypassing RLS, SECURITY DEFINER functions exposed in public schemas, and BOLA/IDOR policy mistakes. - Schema change workflow: Directs agents to iterate with execute_sql or supabase db query, run advisors, then commit clean migrations via supabase db pull. - CLI and MCP guidance: Provides version-aware CLI usage, known gotchas, and step-by-step MCP server troubleshooting. - Use Case: When a user reports that a newly created table is inaccessible via the REST API, the agent checks Data API settings, grants role access, and enables RLS correctly. ## Quick Start Ask the agent to create a new Supabase table with secure RLS policies and expose it to the Data API.

Frequently Asked Questions about supabase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Supabase migration for schema changes?▼

Iterate on schema changes using execute_sql via MCP or supabase db query via CLI, which avoid writing migration history. When ready, run supabase db advisors, then generate the migration with supabase db pull <name> --local --yes and verify with supabase migration list --local.

How do I write secure RLS policies in Supabase?▼

Combine TO authenticated with an ownership predicate like (select auth.uid()) = user_id in the USING clause, and add WITH CHECK for UPDATE policies. Avoid the deprecated auth.role() function and never use user_metadata claims for authorization decisions.

Why is my new Supabase table not accessible via the REST API?▼

Depending on your project's Data API settings, new tables may not be automatically exposed. The anon and authenticated roles need explicit GRANT access, and you should enable RLS when granting public access.

Why do Supabase views bypass my RLS policies?▼

Views bypass RLS by default in Postgres. On Postgres 15 and above, create views with WITH (security_invoker = true); on older versions, revoke access from anon and authenticated roles or move views to an unexposed schema.

How do I troubleshoot the Supabase MCP server connection?▼

First curl https://mcp.supabase.com/mcp and expect a 401 response confirming the server is up. Then verify your .mcp.json configuration, and if tools still are not visible, complete the OAuth 2.1 authentication flow in your agent and reload the session.