supabase

Manage Supabase project lifecycle tasks including schema design, authentication, and security policies.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/betaTrident/manta --skill supabase-betatrident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/betaTrident/manta/tree/main/.agents/skills/supabase
Command: npx skills add https://github.com/betaTrident/manta --skill supabase-betatrident

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill eliminates configuration errors, security vulnerabilities, and implementation delays when working with the Supabase ecosystem by providing verified, version-aware guidance.

Core Features & Use Cases

  • Security Guardrails: Automatically enforces best practices for RLS, JWT claims, and API key management to prevent common data leaks.
  • Schema & Migration Management: Provides safe workflows for database schema changes, ensuring migrations are generated and verified correctly.
  • Use Case: When implementing a new user authentication flow, this skill ensures that your RLS policies are correctly scoped and that sensitive metadata is stored in the appropriate app_metadata fields rather than user_metadata.

Quick Start

Use the supabase skill to audit the current RLS policies on the public schema for potential security vulnerabilities.

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 policies in Supabase to prevent data leaks?

To enforce row level security (RLS) in Supabase, you must configure policies that scope data access using JWT claims. This prevents common data leaks by ensuring API keys are restricted according to current security standards.

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

The best way to manage database schema migrations with Supabase is using safe workflows that generate and verify schema changes. This prevents configuration errors and ensures version-aware compliance across your PostgreSQL database lifecycle.

Why should I store user authentication metadata in app_metadata instead of user_metadata in Supabase?

You should store sensitive user authentication metadata in app_metadata because it prevents clients from altering secure claims. Storing it in user_metadata creates vulnerabilities, whereas app_metadata enforces correct scoping for RLS policies.

Does the Supabase CLI support client-side SDK integrations for web frameworks?

Yes, Supabase operates across the CLI, MCP server, and client-side SDK integrations for web frameworks. This ensures authentication configuration and security policies comply with version-specific API conventions.

How do I audit existing RLS policies on a public schema for vulnerabilities?

To audit existing RLS policies on a public schema for vulnerabilities, you review policy definitions against current security standards. This identifies misconfigurations in JWT claims and API key management that could expose data.