supabase-rls-check
Skill65 starsChanged 14 days agoMITView on GitHub
Use when the user asks whether Supabase tables are missing RLS, whether a policy lets everyone read or write (using true), why a query fails with 42501 permission denied, whether a security definer function is callable with the anon key, or wants an RLS check of their Supabase migrations before deploy. Runs the free local VibeRaven repo check on the migration files, with no login and no database credentials. Not a live database or penetration test.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/viberaven-core.mdcCursor rule
- .cursor/rules/viberaven-deploy.mdcCursor rule
- .cursor/rules/viberaven-payments.mdcCursor rule
- .cursor/rules/viberaven-supabase-rls.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
- viberavenSkill
- viberavenSkill
- architecture-contextSkill
- architecture-planSkill
- go-liveSkill
- production-contextSkill
- vercel-supabase-launch-checkSkill
- viberavenSkill
- what-brokeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the Supabase migrations in this repository and list the tables and functions that real users could reach without the right row-level …
- Distinctive: line 24
Re-check once per batch of fixes,: not after every edit.
- Distinctive: line 29
Do not say the database is secure because the check found nothing.
- Distinctive: line 30
Do not disable RLS or drop a policy to make a 42501 error go away.
- Very specific: line 31
Do not ask for database credentials or print keys.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Supabase RLS check
Commands pin published CLI 1.8.0, re-run on a fixture on 2026-11-09. This checks repository files, not the live database.
Read the Supabase migrations in this repository and list the tables and functions that real users could reach without the right row-level security.
Steps
- Run the check in the project root:
Exit code 1 means it found blockers. That is a result, not a crash. Ifnpx -y viberaven@1.8.0 checkviberaven_check_readinessis in your tool list (the local VibeRaven MCP server), you can call it on the project root instead. - Read the RLS findings in the output and in
.viberaven/agent-tasklist.md:rls_disabled: a table created in a migration with RLS never enabled.rls_policy_allows_all_read/rls_policy_allows_all_write: a policy withusing (true)orwith check (true). Readqual, not the policy name.- Grants and security definer findings: a table the client reads without a grant (the 42501 case), or a function anyone holding the anon key can call.
- Fix one gap at a time with a new migration, and show the user the diff. Enabling RLS on a table with no policies blocks all client reads, so ask the user before applying that one.
- Re-check once per batch of fixes, not after every edit.
- Say what the check cannot see. Policies changed only in the Supabase dashboard are invisible to a repo check. If the user already connected the official Supabase MCP server, compare with its read-only
get_advisors(typesecurity) andlist_tables.
Do not
- Do not say the database is secure because the check found nothing. It means the migration files had no RLS gaps it checks for.
- Do not disable RLS or drop a policy to make a 42501 error go away.
- Do not ask for database credentials or print keys. VibeRaven never needs them.
For the full Vercel + Supabase launch pass (keys in client code, env vars, Stripe webhooks), use the vercel-supabase-launch-check skill.
More: https://viberaven.dev/supabase-rls-checker and https://viberaven.dev/llms.txt
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

