Claude Skill

supabase-operator

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

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_supabase-operator-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 5d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/supabase-operator

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Confirm project ref / linked CLI or MCP.
Inspect tables, policies, and functions relevant to the task.
For schema changes: write a migration; never hot-edit prod casually.
Verify RLS: who can select/insert/update/delete.
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).

Files (navin)

SKILL.md 1.1 KB

---
name: supabase-operator
description: Administer Supabase tables, migrations, storage, functions, and RLS policies. Prefer MCP Supabase or CLI when configured.
metadata: {"navin":{"emoji":"⚡","category":"data"}}
---

# 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).