Back to catalog / Integrations
Supabase Project Development and Operations
Handle Supabase Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, and client integration tasks.
Skills
Before implementing, read the current Supabase changelog and product docs rather than relying on stale assumptions. Treat Data API exposure and RLS as separate gates; identify the project ref, CLI/MCP context, and environment. Present a plan and use least privilege before changing schemas, migrations, Auth, Storage, or Edge Functions. Verify each change with targeted queries or integration tests; after two or three failures, change the diagnosis instead of looping retries.
Permissions
Prerequisites
- Current Supabase docs and a specific project; remote actions need authenticated access through Supabase CLI or MCP.
Permissions
- Connected tools may read or write schema, data, policies, or keys within their access. Confirm project/environment before access and get explicit approval before remote changes or deployment.
Limitations
APIs and configuration change; follow the current official changelog/docs. Data API settings differ by project.
Pinned upstream source
- Repository
- openai/plugins
- File path
- plugins/supabase/skills/supabase/SKILL.md
- Pinned commit
0722921d5542fc593105c27bd52630babd8b8c2a- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Codex · Supabase CLI · Supabase MCP
Main topic
Take a coding Agent change from context to verification