Skill · em Construir backend e dados
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions,…
Procedência
- Origem: supabase/agent-skills
- Caminho:
skills/supabase - Versão fixada:
551274ed2fe97c8fea1325f7ceb05803a542f8df - Licença: MIT
- Espelhado em 25/09/2026
- 291,4 mil instalações no skills.sh (lido em 25/09/2026)
Antes de instalar
4 arquivos · 22,6 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 551274e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/skills/supabase/.
d=".claude/skills/supabase" u="https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/skills/supabase" curl -fsSL --create-dirs \ -o "$d/SKILL.md" "$u/SKILL.md" \ -o "$d/assets/feedback-issue-template.md" "$u/assets/feedback-issue-template.md" \ -o "$d/CHANGELOG.md" "$u/CHANGELOG.md" \ -o "$d/references/skill-feedback.md" "$u/references/skill-feedback.md" \ -o "$d/LICENSE" "https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/LICENSE"
Global: instala em ~/.claude/skills/supabase/.
d="$HOME/.claude/skills/supabase" u="https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/skills/supabase" curl -fsSL --create-dirs \ -o "$d/SKILL.md" "$u/SKILL.md" \ -o "$d/assets/feedback-issue-template.md" "$u/assets/feedback-issue-template.md" \ -o "$d/CHANGELOG.md" "$u/CHANGELOG.md" \ -o "$d/references/skill-feedback.md" "$u/references/skill-feedback.md" \ -o "$d/LICENSE" "https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/LICENSE"
Codex
Neste projeto: instala em .agents/skills/supabase/.
d=".agents/skills/supabase" u="https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/skills/supabase" curl -fsSL --create-dirs \ -o "$d/SKILL.md" "$u/SKILL.md" \ -o "$d/assets/feedback-issue-template.md" "$u/assets/feedback-issue-template.md" \ -o "$d/CHANGELOG.md" "$u/CHANGELOG.md" \ -o "$d/references/skill-feedback.md" "$u/references/skill-feedback.md" \ -o "$d/LICENSE" "https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/LICENSE"
Global: instala em ~/.agents/skills/supabase/.
d="$HOME/.agents/skills/supabase" u="https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/skills/supabase" curl -fsSL --create-dirs \ -o "$d/SKILL.md" "$u/SKILL.md" \ -o "$d/assets/feedback-issue-template.md" "$u/assets/feedback-issue-template.md" \ -o "$d/CHANGELOG.md" "$u/CHANGELOG.md" \ -o "$d/references/skill-feedback.md" "$u/references/skill-feedback.md" \ -o "$d/LICENSE" "https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/LICENSE"
Antigravity
Neste projeto: instala em .agents/skills/supabase/.
d=".agents/skills/supabase" u="https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/skills/supabase" curl -fsSL --create-dirs \ -o "$d/SKILL.md" "$u/SKILL.md" \ -o "$d/assets/feedback-issue-template.md" "$u/assets/feedback-issue-template.md" \ -o "$d/CHANGELOG.md" "$u/CHANGELOG.md" \ -o "$d/references/skill-feedback.md" "$u/references/skill-feedback.md" \ -o "$d/LICENSE" "https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/LICENSE"
Global: instala em ~/.gemini/antigravity-cli/skills/supabase/.
d="$HOME/.gemini/antigravity-cli/skills/supabase" u="https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/skills/supabase" curl -fsSL --create-dirs \ -o "$d/SKILL.md" "$u/SKILL.md" \ -o "$d/assets/feedback-issue-template.md" "$u/assets/feedback-issue-template.md" \ -o "$d/CHANGELOG.md" "$u/CHANGELOG.md" \ -o "$d/references/skill-feedback.md" "$u/references/skill-feedback.md" \ -o "$d/LICENSE" "https://raw.githubusercontent.com/supabase/agent-skills/551274ed2fe97c8fea1325f7ceb05803a542f8df/LICENSE"
Peça ao Rook
Já usa o Rook Labs? Cole no chat do Rook: instale a skill https://rooklabs.sh/marketplace/supabase.agent-skills.supabase
Prévia do SKILL.md
---
name: supabase
description: "Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cook…
metadata:
author: supabase
version: "0.1.2"
---
# Supabase
## Core Principles
**1. Supabase changes frequently — verify against changelog and current docs before implementing.**
Do not rely on training data for Supabase features. Function signatures, config.toml settings, and API conventions change between versions.
First, fetch `https://supabase.com/changelog.md` (a lightweight summary index — not a heavy pull), scan for `breaking-change` tags relevant to your task, and follow the linked page for any that apply. Then look up the relevant topic using the documentation access methods below.
**2. Verify your work.**
After implementing any fix, run a test query to confirm the change works. A fix without verification is incomplete.
**3. Recover from errors, don't loop.**
If an approach fails after 2-3 attempts, stop and reconsider. Try a different method, check documentation, inspect the error more carefully, and review relevant logs when available. Supabase issues are not always solved by retrying the same command, and the answer is not always in the logs, but logs are often worth che…
**4. Exposing tables to the Data API:** Depending on the user's [Data API settings](https://supabase.com/dashboard/project/<ref>/integrations/data_api/settings), newly created tables may not be automatically exposed via the Data (REST) API. If this is the case, `anon` and `authenticated` roles will need to be explicitl…
> Note that this is separate from RLS, which controls which _rows_ are visible once a table is accessible, not whether the table is accessible at all.
When a user reports a SQL-created table is unexpectedly inaccessible, check their Data API settings and whether the roles have been granted access via explicit `GRANT` SQL. When granting public (`anon`/`authenticated`) access, always enable RLS too. See [Exposing a Table to the Data API](https://supabase.com/docs/guide…
**5. RLS in exposed schemas.**
…