supabase

Guide secure Supabase setup and troubleshooting across database, auth, and integration layers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you implement Supabase features safely and correctly by providing up-to-date, practice-focused guidance for common database, auth, RLS, migrations, and integration tasks.

Core Features & Use Cases

  • Supabase change-proofing: Guides you to verify breaking changes via the Supabase changelog before implementing anything that depends on current behavior.
  • RLS and security correctness: Covers frequent authorization traps (JWT claims, service_role exposure, view RLS behavior, UPDATE requiring SELECT policy) with a targeted security checklist.
  • Operational workflow for schema changes: Recommends safe iteration via direct SQL execution and a clean migration workflow once ready.

Use case examples: Debug why a user can’t log in due to session/JWT/RLS configuration, design policies for exposed schemas so tables are accessible through the Data API, or safely create migrations and verify advisors before rollout.

Quick Start

Use the supabase skill to design and implement the required RLS policies and migration steps for a table you want accessible through Supabase Data API.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I fix Supabase RLS policies blocking access through the Data API?

To fix Supabase RLS blocking the Data API, design policies for exposed schemas ensuring UPDATE operations include matching SELECT policies. Verify JWT claims and avoid service_role exposure to maintain secure authorization.

Why does my Supabase user session break in Next.js SSR?

Supabase user sessions break in Next.js SSR when @supabase/ssr client usage or auth configuration is incorrect. Troubleshoot by verifying session handling, checking JWT validity, and ensuring RLS configurations align with server-side rendering requirements.

What is the safest workflow for Supabase database migrations?

The safest workflow for Supabase database migrations involves iterating via direct SQL execution first, then generating clean migrations using the CLI or MCP once ready. Always verify breaking changes via the changelog and check advisors before rollout.

Does the Supabase CLI support safe schema changes with MCP integration?

Yes, the Supabase CLI supports safe schema changes with MCP integration by enabling deterministic CLI/MCP discovery, safe SQL iteration, and migration generation with verification. This workflow ensures secure, version-aware setup and troubleshooting.

When do I need to check the Supabase changelog before implementing features?

You need to check the Supabase changelog before implementing features whenever your task depends on current behavior, ensuring change-proofing against breaking updates. This practice-focused guidance prevents integration failures across database, auth, and RLS layers.