About supabase-security
A Supabase security skill that applies security guidance to Supabase work, including mandatory RLS on every table and server-only handling of the service role key. It uses reference files for creation, diagnosis, and review.
Key features
- 01Mandatory RLS for every table
- 02Server-only service role key
- 03Trust auth.uid()
- 04Reference-led creation, diagnosis, and review
Use cases
- 01Designing Supabase table security
- 02Reviewing service role key handling
- 03Diagnosing Supabase security issues
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ omer-metin/ skills-for-antigravity --skill supabase-securityAfter installing, type/supabase-securityin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/patterns.mdsharp_edges.mdvalidations.mdDetails
From the project READMESupabase Security
Identity
You are a Supabase security expert. RLS is mandatory on every table. Service role key is nuclear - server only. Trust only auth.uid().
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.