supabase

Troubleshoot and implement Supabase schema, RLS, and auth changes with verification.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill supabase-otto-poblysh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/otto-poblysh/pedagemy-early-access/tree/main/.agents/skills/supabase
Command: npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill supabase-otto-poblysh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps you implement and troubleshoot Supabase features (especially database schema, RLS, auth, and server-side writes) without making common security mistakes or getting stuck on version-specific CLI/MCP behaviors.

Core Features & Use Cases

  • Supabase security guardrails: Ensures you verify RLS exposure rules, avoid leaking service-role secrets, and use safe authorization data patterns.
  • Reliable troubleshooting workflow: Guides structured debugging for auth/session issues, Data API exposure problems, and common RLS edge cases.
  • Schema change best practices: Recommends correct workflows for iterating SQL, then generating migrations safely with verification steps.
  • Doc-first implementation: Directs you to fetch the right Supabase documentation via MCP search or docs-as-markdown to avoid outdated assumptions.
  • Works across tools: Covers Supabase CLI discovery, CLI gotchas, and MCP connection/auth troubleshooting.

Quick Start

Apply the right RLS and Data API permissions for the change you made in Supabase, then verify the behavior with a targeted test query and checks for exposed-schema access.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I safely implement Supabase schema migrations and RLS policies?

To implement Supabase RLS policies securely, verify exposure rules, avoid leaking service-role secrets, and use safe authorization data patterns. Validate outcomes by running targeted test queries to check for exposed-schema access.

Why does my Supabase Data API expose schema access after auth changes?

Supabase Data API exposure issues often occur when RLS policies and API permissions are not updated together. You need to apply the right RLS and Data API permissions for your changes, then verify behavior with targeted test queries.

What is the best way to troubleshoot Supabase auth and session issues in Next.js SSR?

The best way to troubleshoot Supabase auth and session issues in Next.js SSR is using a structured debugging workflow. Verify safe authorization data patterns and strict secret handling to isolate session edge cases.

Does the Supabase CLI have common gotchas with MCP connection and auth operations?

Yes, the Supabase CLI has version-specific gotchas regarding MCP connection and auth operations. Fetch the right Supabase documentation via MCP search or docs-as-markdown to avoid outdated assumptions and verify CLI behaviors.

How do I avoid leaking service-role secrets during Supabase server-side writes?

To avoid leaking service-role secrets during Supabase server-side writes, adhere to strict secret handling and RLS security checklists. Always use safe authorization data patterns and verify access with test queries.