supabase

Guide secure Supabase implementation across database, auth, API, and storage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ebarroso12/personal-skills --skill supabase-ebarroso12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/ebarroso12/personal-skills/tree/main/supabase
Command: npx skills add https://github.com/ebarroso12/personal-skills --skill supabase-ebarroso12

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you implement Supabase features correctly and safely by guiding you through version-aware setup, verification, and security best practices for database, auth, and API access.

Core Features & Use Cases

  • Supabase change-proofing: Verifies breaking changes by checking the Supabase changelog before implementing.
  • Reliability through validation: Ensures fixes are confirmed with test queries instead of assumptions.
  • Security-first guidance: Covers RLS correctness, Data API exposure, JWT/auth pitfalls, views and security definer gotchas, and storage permission requirements.
  • Workflow coverage: Addresses common tasks across Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues) plus CLI and Supabase MCP server usage.
  • Schema & migration practices: Recommends safe iteration (SQL execution) and a disciplined path to committing schema changes via migrations.

Quick Start

Use the supabase skill when you need help fixing a login/session or RLS policy issue for your Supabase project.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I write secure Supabase RLS policies for Postgres tables?

Supabase RLS policies require adherence to safe auth claims and specific security constraints to prevent data exposure. You must verify policy patterns, view security definer gotchas, and Data API table exposure rules to ensure correct access control.

Why does my Supabase authentication session break or fail JWT validation?

Supabase authentication failures often stem from JWT/session troubleshooting pitfalls and unsafe auth claims usage. Resolving these requires version-aware documentation checks and verifying auth fixes with test queries rather than assumptions.

What is the best way to manage Supabase schema migrations and CLI operations?

Managing Supabase schema migrations requires executing SQL for safe iteration, then committing changes via a disciplined migration workflow. This approach ensures reliable database updates alongside Supabase CLI or MCP server operations.

Does the Supabase Data API expose my tables if I disable row level security?

Disabling row level security exposes your tables through the Supabase Data API. Configuring correct RLS policies and verifying table exposure rules are required to prevent unauthorized API access to your Postgres data.

Can I use Supabase storage and Edge Functions without encountering security definer gotchas?

Using Supabase storage and Edge Functions safely requires adherence to storage permission rules and avoiding view security definer gotchas. You must verify configurations with test queries to ensure correct access control.