# Supabase Operator

> Administer Supabase tables, migrations, storage, functions, and RLS policies. Prefer MCP Supabase or CLI when configured.

- Skill: `navinspire-ia/supabase-operator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add navinspire-ia/supabase-operator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/navinspire-ia/supabase-operator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Navinspire-ia (https://skillmd.com/u/navinspire-ia)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/navinspire-ia/supabase-operator

---


# Supabase Operator

## Overview

Treat RLS as part of the product. Schema changes go through migrations.

## Tools

For SQL, use the built-in `db_query` tool with a connection configured as `{"engine": "supabase", "url": "<Supabase Postgres connection string>"}` under `tools.database.connections` (read-only unless `allowWrites`). Use the Supabase CLI or MCP server for migrations, storage, and edge functions.

## Workflow

1. Confirm project ref / linked CLI or MCP.
2. Inspect tables, policies, and functions relevant to the task.
3. For schema changes: write a migration; never hot-edit prod casually.
4. Verify RLS: who can select/insert/update/delete.
5. Storage buckets: check public vs private; signed URLs for private objects.

## Rules

- Service-role keys are secrets - never expose to clients or chat.
- Policy tightening/loosening needs review (`human-approval` on prod).