Supabase Audit Tables List
ListedHelps 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-tables-list -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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: abc123def.supabase.co.
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.
Hosts contacted
abc123def.supabase.coundeclaredWhat it found
- skills/audit-api/supabase-audit-tables-list/SKILL.md:336contacts abc123def.supabase.co
"curl_command": "curl -s 'https://abc123def.supabase.co/rest/v1/' -H 'apikey: $ANON_KEY'"
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 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, 348 lines
About this skill
The supabase-audit-tables-list skill enables AI agents to automatically discover and enumerate all tables within a Supabase project. It provides a comprehensive inventory of database schemas, allowing agents to understand the data structure before performing security audits or penetration tests. This capability is essential for mapping out potential attack surfaces in cloud-based PostgreSQL databases managed by Supabase.
When to use it
- Initiating a security assessment to identify which tables hold sensitive user data or credentials.
- Generating a baseline schema report to compare against expected production configurations.
- Preparing an AI agent to write specific SQL queries for vulnerability scanning across known datasets.
- Validating that unauthorized tables have not been created during recent deployments.
Key capabilities
- Automatically lists every table name available in the connected Supabase instance.
- Provides a structured overview of the database schema without requiring manual inspection.
- Integrates directly with Supabase's metadata to ensure real-time accuracy of table inventories.
Example prompts
- "List all tables in my Supabase project so I can begin reviewing them for SQL injection vulnerabilities."
- "Generate a report of every table name and its associated schema details from this Supabase connection."
- "Identify all user-related tables in the database to prepare for a privacy compliance audit."
Tips & gotchas
Ensure your AI agent has the necessary read permissions on the Supabase project, as listing tables requires access to the underlying PostgreSQL metadata. This skill only reveals table names and does not expose column data or row contents unless explicitly queried separately.