CarolMonroe22

Supabase DB Supervisor — Data skill for Claude Code

Data community

Fresh-eyes supervision pass for AI-built database work.

How to install Supabase DB Supervisor

This entry records only its repository, not the path inside it, so there is no exact command to give. Open CarolMonroe22/supabase-db-supervisor and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Supabase DB Supervisor does

Fresh-eyes supervision pass for AI-built database work. The builder never grades its own homework.

Alternatives in Data

  • Data Contract — This document defines which files belong to the system (auto-updatable) and which belong to the user (never to 32.5k ★
  • MCP Server Supabase — Supabase database and auth integration 2.6k ★
  • Pipeline Feature — Add a feature to the FFmpeg transcode pipeline following Tunarr's pipeline builder pattern 2.5k ★

README

db-supervisor: the builder never grades its own homework

License: MIT Status: work in progress PRs welcome

supabase-db-supervisor

An agent skill that adds a **fresh-eyes supervision pass** to any database work an AI agent builds. A separate agent plays the investigator, proves who can see which data with real queries, and gives an explicit OK before anything ships. The builder never grades its own homework.

**Status: work in progress.** This is v0.1, a starting point published in the open. The checklist, routing logic, and output format will evolve. Issues and PRs welcome.

Why

[Supabase Evals](https://supabase.com/evals) (open sourced July 2026) measured how well coding agents build real Supabase backends across four stages. The headline:

Stage What it means Top agents
Build Create schema, auth, RLS from scratch ~100%
Deploy Ship it live with secrets and monitoring ~100%
Investigate Something broke, find out why 67% for most
Resolve Fix it without breaking more ~100%

Agents are excellent at the part where you feel productive, and weakest at the part where you feel lost. This skill moves the Investigate stage inside the build loop, so the gap gets covered before anything ships instead of at 11pm when it breaks.

How it works

flowchart LR
    A[Agent builds
database work] --> B[Fresh-context
supervisor] B --> C[Access proofs
real queries] B --> D[Advisors
security + perf] B --> E[Migrations
vs reality] B --> F[Upstream
freshness] C --> V{VERDICT} D --> V E --> V F --> V V -->|OK| S[Ship 🏁] V -->|NEEDS ATTENTION| R[Fix +