supabase

Develop, deploy, and administer Supabase projects across managed and self-hosted environments.

40|6|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/magnus919/agent-skills --skill supabase-magnus919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase
Source: https://github.com/magnus919/agent-skills/tree/main/supabase
Command: npx skills add https://github.com/magnus919/agent-skills --skill supabase-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of managing Supabase across different environments, preventing common pitfalls like configuration drift, insecure key handling, and broken service boundaries.

Core Features & Use Cases

  • Full-Lifecycle Management: Provides evidence-led workflows for managed projects, local CLI development, and self-hosted Docker stacks.
  • Database & Security Hardening: Automates schema migrations, RLS policy testing, and secure key management to ensure production-grade reliability.
  • Use Case: Use this skill to safely upgrade a self-hosted Postgres 15 instance to 17, or to verify that your RLS policies correctly block unauthorized access to sensitive user data.

Quick Start

Use the supabase skill to initialize a new local project and run the database migration suite to verify your current schema.

Frequently Asked Questions about supabase

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

FAQPage Schema
How do I manage Supabase schema migrations across local and self-hosted Docker environments?

You can manage Supabase schema migrations across environments using evidence-led workflows for local CLI development and self-hosted Docker stacks. This prevents configuration drift and ensures production-grade reliability during deployment.

How do I test RLS policies to ensure they block unauthorized access to user data?

RLS policy testing is handled through database and security hardening workflows that verify your rules correctly block unauthorized access. This ensures sensitive user data remains protected in production.

Can I use this to safely upgrade a self-hosted Postgres 15 instance to 17?

Yes, you can safely upgrade a self-hosted Postgres 15 instance to 17 using the provided full-lifecycle management workflows. This ensures service boundaries remain intact and operational continuity is preserved.

What is the best way to handle secure key management for Supabase backend infrastructure?

Secure key management is implemented through database and security hardening processes that prevent insecure key handling. This approach ensures production-grade reliability and adherence to security best practices.

Does this support cross-service troubleshooting for managed Supabase projects?

Yes, cross-service troubleshooting is supported for managed projects, local CLI development, and self-hosted Docker stacks. It includes service-level health monitoring to identify and resolve broken service boundaries.

Why do I need backup verification for self-hosted PostgreSQL databases?

Backup verification is required to ensure adherence to security best practices and maintain production-grade reliability. It confirms your backup strategy works before a critical failure occurs in your self-hosted environment.