Supabase Audit Rls
CheckedHelps with Supabase, auditing as part of working with databases and data persistence workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-audit-rls -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
yoanbernabeu
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned yoanbernabeu/supabase-pentest-skills at 0f9612276b.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0f9612276b
- Scanned
- 1 file, 399 lines
About this skill
What it does
This skill enables AI agents to audit Row Level Security (RLS) policies within Supabase databases, ensuring data access rules are correctly configured. It helps identify potential security vulnerabilities or misconfigurations that could expose sensitive information to unauthorized users.
When to use it
- Before deploying a new Supabase project to production to validate initial security settings.
- During routine maintenance to verify that RLS policies still align with updated business logic.
- When investigating suspected data leaks to check if policy gaps allowed unauthorized access.
- As part of a penetration testing workflow to simulate and detect privilege escalation attempts.
Key capabilities
- Analyzes existing Row Level Security policies for logical errors or overly permissive rules.
- Identifies missing policies that should restrict access to specific data rows based on user roles.
- Evaluates policy definitions against best practices for Supabase security architecture.
Example prompts
- "Audit the RLS policies in my Supabase project and list any rules that allow public read access to private tables."
- "Check if my current Row Level Security configuration properly restricts users from viewing other users' records."
- "Review the database schema and suggest missing RLS policies needed to enforce role-based data isolation."
Tips & gotchas
Ensure you have appropriate read permissions on the Supabase project before running an audit, as the agent needs access to policy definitions. This skill focuses on logical analysis of rules rather than executing database commands directly.