supabase

Guide secure Supabase schema, auth, RLS, and Data API implementation.

3|Updated May 3, 2026
One-click install
npx skills add https://github.com/ductoanoxo/Agent_SQL --skill supabase-ductoanoxo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/ductoanoxo/Agent_SQL/tree/main/.agents/skills/supabase
Command: npx skills add https://github.com/ductoanoxo/Agent_SQL --skill supabase-ductoanoxo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It prevents common Supabase security, RLS, Data API exposure, and auth integration mistakes that can break features or create vulnerabilities.

Core Features & Use Cases

  • RLS and Data API correctness: Ensures tables in exposed schemas are accessible via the Data API and that row-level visibility is enforced with appropriate policies.
  • Supabase-specific security guardrails: Covers JWT/session pitfalls, service role safety, view behavior with RLS, update/select policy interactions, and storage upsert permissions.
  • Operational troubleshooting guidance: Provides safe workflows for Supabase CLI usage, MCP server connectivity, documentation discovery, and error recovery without retry loops.

Quick Start

Use the supabase skill when asked to help set up, debug, or secure a Supabase feature involving auth, RLS, schema changes, Data API exposure, storage, or Postgres extensions.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I enforce row-level security in Supabase for exposed schemas?

Supabase row-level security (RLS) requires configuring appropriate policies on tables in exposed schemas to control visibility via the Data API. This ensures row-level access is enforced and prevents unauthorized data exposure.

Why does my Supabase auth integration break in Next.js SSR?

Supabase auth integration in Next.js SSR often breaks due to JWT and session handling pitfalls. You need to follow specific security guardrails for client integration to ensure server-side rendering maintains secure session data.

What is the best way to manage Postgres schema migrations with the Supabase CLI?

Managing Postgres schema migrations with the Supabase CLI involves using safe operational workflows for database changes. This process includes running validation after fixes and verifying changes against the official changelog to ensure schema integrity.

Can I use Supabase storage upserts with RLS policies enabled?

You can use Supabase storage upserts with RLS policies enabled by applying specific storage upsert permissions. Security best practices must be enforced to ensure that row-level security rules correctly govern file storage operations.

How do I troubleshoot Supabase MCP server connectivity without retry loops?

Troubleshooting Supabase MCP server connectivity without retry loops requires following safe operational workflows for error recovery. This approach provides documentation discovery and guidance to resolve connection issues directly without causing infinite retry cycles.

When do I need to verify Supabase schema changes against the changelog?

You need to verify Supabase schema changes against the changelog whenever modifying database features, auth configurations, or RLS policies. This validation step ensures changes align with current documentation and prevents breaking updates.