supabase / agent-skills

The supabase skill is the broad one: every product surface — Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues — the client libraries and SSR integrations for Next.js, React, SvelteKit, Astro, and Remix, the CLI and MCP server, schema changes and migrations, and the debugging path through auth failures, RLS surprises, schema-cache issues, and Postgres, HTTP, or Edge Function errors down to reading the logs in ClickHouse.

supabase-postgres-best-practices is narrower and, by its own description, not Supabase-specific at all — it is Postgres guidance for Postgres running anywhere, organized into eight categories from query performance and connection management, marked critical, down to monitoring and advanced features, marked low priority. Its own text is explicit that even a one-column change or a single query deserves these rules, not just a big schema migration.

READ THE FULL ANALYSIS＋

What each one costs to start. The supabase skill assumes the CLI or MCP server is already part of your workflow — our dependency check labels it local_tool. The Postgres best-practices skill is pure written reference: nothing to install, nothing to authenticate, labelled ready.

Distribution is unusually tight for a two-skill package. It installs through npx skills add supabase/agent-skills, through a Claude Code plugin marketplace (claude plugin install supabase@supabase-agent-skills), and — per the README — every release also publishes a dist/index.json file that supabase.com itself reads to serve these same two skills at its own .well-known/agent-skills endpoint. The skill package and the vendor's documentation site are built from one source.