This skill decides how a product uses Supabase before the agent follows API guidance: who holds the secret key, what RLS is for, how migrations are delivered, and whether a push applies them. Where Supabase’s defaults or quickstarts disagree, this skill wins.
It sets ten choices, a setup order for the first time, rules for scheduled SQL with pg_cron, a promotion routine that reads the migration ledger first, and a record of every dashboard setting with its verification date.
What You Get
- Ten numbered choices covering keys, RLS, identity tokens, migration files, CLI targets, the MCP, pushes and compatibility
- A first-time setup in four steps with a verified development target
- A promotion routine: read the ledger, check the window, apply on the owner’s go, prove code and schema agree
- Rules for scheduled SQL, including a catalog assertion and an outside witness
- Reference files for the access model, migrations, projects and backups, and gotchas
Common Use Cases
- Setting up a Supabase project for a Next.js product with server-side access only
- Writing and applying a migration without linking the CLI
- Promoting a release with pending migrations while old builds still serve
- Scheduling a pg_cron job and watching that it runs
What Makes It Unique
It tells the agent to refuse some Supabase suggestions: browser keys, RLS policies that mimic an access model, applying a migration through the MCP, and supabase link. RLS is on with zero policies, so tenant isolation lives in the three authorization functions and not in the database policies.
Under The Hood
The skill is instructions and reference markdown, with no scripts. Following it, the agent runs the Supabase CLI against a database URL it is given for each command, installs Supabase’s own skills with the skills CLI from GitHub, runs migrations and tests, and edits code, migration files and the product’s environment, integration and permission docs. It handles connection strings and keys that the owner supplies from an uncommitted operator file. The MCP is used read-only, for logs and advisors on a development project.