← marketplace
engineersplatformsha:5fb1181d415473b3manual
supabase-agent-skills
Use when an AI agent needs grounded Supabase knowledge — Postgres, Auth, RLS, Storage, Edge Functions, Realtime, Vectors, Cron, and Queues — installed as official skills.
Install confidence
reviewedsource repo
curl --create-dirs -fsSL https://skillmake.xyz/i/supabase-agent-skills -o ~/.claude/skills/supabase-agent-skills/SKILL.md
Pinned content
sha:5fb1181d415473b3
Generated with
manual
Source
github.com
The file served at /api/marketplace/supabase-agent-skills-5fb1181d/raw matches this hash. Inspect before install, then copy the command.
4,011 chars · ~1,003 tokens
--- name: supabase-agent-skills description: Use when an AI agent needs grounded Supabase knowledge — Postgres, Auth, RLS, Storage, Edge Functions, Realtime, Vectors, Cron, and Queues — installed as official skills. source: https://github.com/supabase/agent-skills generated: 2026-05-17T04:18:37.627Z category: platform audience: engineers --- ## When to use - Bootstrapping a new Supabase project with an AI coding agent - Debugging auth issues — sessions, JWTs, cookies, getUser, getClaims - Writing or auditing Row Level Security policies - Tuning Postgres query performance and connection pooling on Supabase - Deploying Edge Functions or wiring Realtime subscriptions - Choosing between client-side and SSR Supabase clients in Next.js - Reviewing schema design and concurrency patterns before scale ## Key concepts ### supabase skill The comprehensive skill covering all Supabase products: Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, and Queues. It also covers client libraries and SSR integrations so the agent knows when to reach for supabase-js vs @supabase/ssr. ### supabase-postgres-best-practices Performance optimization guide organized into 8 categories: Query Performance, Connection Management, Schema Design, Concurrency & Locking, Security & RLS, Data Access Patterns, Monitoring & Diagnostics, and Advanced Features. Used as a checklist when reviewing schemas, indexes, and queries. ### Agent Skills Open Standard Every skill in the repo follows the Agent Skills Open Standard: a SKILL.md manifest with frontmatter is required, and a references/ folder holds optional deep docs. This makes skills portable across Claude Code, Cursor, Cline, GitHub Copilot, and 18+ other agents. ### Auth troubleshooting surface The supabase skill explicitly scopes auth troubleshooting to login, logout, sessions, JWT handling, cookies, getSession, getUser, getClaims, and RLS — so the agent stops at the right boundary instead of inventing fixes for unrelated symptoms. ### Claude Code plugin marketplace In addition to the generic skills installer, Supabase ships the same content as a Claude Code plugin. The plugin marketplace command registers the source, and a second install command pins the specific plugin id so updates flow through Claude Code's plugin system. ## API reference ``` npx skills add supabase/agent-skills ``` Install every skill from supabase/agent-skills into the local agent. ``` npx skills add supabase/agent-skills ``` ``` npx skills add supabase/agent-skills --skill <name> ``` Install only one skill — for example just supabase or just supabase-postgres-best-practices. ``` npx skills add supabase/agent-skills --skill supabase ``` ``` claude plugin marketplace add / plugin install ``` Register supabase/agent-skills as a Claude Code plugin marketplace source, then install the supabase plugin from it so it tracks updates via Claude Code. ``` claude plugin marketplace add supabase/agent-skills claude plugin install supabase@supabase-agent-skills ``` ## Gotchas - Skills are passive — they only fire when the agent detects a Supabase task; do not expect them to run on every prompt - Use Supabase's official MCP / skill rather than scraping the public docs; the skill is the canonical source - RLS policies are part of the auth troubleshooting surface — fixing 'permission denied' often means editing policy SQL, not changing client code - @supabase/ssr is a different package from @supabase/supabase-js; mixing them in a Next.js app breaks cookie-based sessions - Edge Functions, Realtime, and Storage each have their own quotas and gotchas — do not treat them as a single 'Supabase' surface - Performance issues usually trace back to one of the 8 Postgres categories (queries, connections, schema, concurrency, security, access, monitoring, advanced) — diagnose in that order --- Generated by SkillMake from https://github.com/supabase/agent-skills on 2026-05-17T04:18:37.627Z. Verify against source before relying on details.
File: ~/.claude/skills/supabase-agent-skills/SKILL.md