Supabase native skills
Version baseline: Supabase CLI v2, supabase-js v2, and the current CLI local Postgres 17 line. Hosted project Postgres versions and client libraries remain independently versioned.
Inspect before installing
- Read the lockfile,
supabase/config.toml, migration history, and installed CLI version. - Determine the linked project's Postgres major with a read-only query when access is already available; do not reveal credentials.
- Inspect existing agent skill locations and any installed Supabase skill source metadata.
- Read the current Supabase AI Skills documentation and first-party
supabase/agent-skillsrepository.
Enforce baseline compatibility
- Require the main
supabaseskill to support CLI v2 andsupabase-jsv2 patterns. - Check SQL and migration advice against the actual hosted Postgres major; do not assume the local CLI image and remote project match.
- Treat
supabase-postgres-best-practicesas database guidance, not as permission to bypass RLS or mutate a remote project. - Reject guidance that invents CLI commands, disables RLS, uses legacy auth helpers, or assumes a service-role key belongs in the browser.
- Do not upgrade the CLI, clients, Postgres major, or installed skills without an explicit request.
Install only on request
Choose only the skills relevant to the project:
npx skills add supabase/agent-skills --skill supabase
npx skills add supabase/agent-skills --skill supabase-postgres-best-practices
Install the complete first-party collection only if the user asks:
npx skills add supabase/agent-skills
Let the user choose agent and project/user scope. Review the selected SKILL.md and any bundled scripts before allowing execution or overwriting an existing installation.
Verify
Report the source, selected skills, destination and scope, release or revision, CLI/client/Postgres versions, and compatibility result. If local and hosted Postgres majors differ, state which guidance applies to each. Leave incompatible skills unchanged and explain the mismatch.