Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Audit Authenticated

Checked
yoanbernabeu·vlatest·database

Helps with Supabase, auditing as part of working with databases and data persistence workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-audit-authenticated -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to 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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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
Manifest
skills/audit-auth/supabase-audit-authenticated/SKILL.md
Scanned
1 file, 472 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The supabase-audit-authenticated skill enables AI agents to perform security audits on Supabase projects by executing authenticated queries. It allows the agent to inspect database schemas, review row-level security policies, and analyze user access configurations directly within the environment.

When to use it

  • Verifying that Row Level Security (RLS) policies correctly restrict data access for different user roles.
  • Auditing existing database tables and views to identify potential schema vulnerabilities or overly permissive settings.
  • Checking authentication provider configurations to ensure only authorized users can interact with the database.
  • Validating that service role keys are not exposed in application code or environment variables accessible to the agent.

Key capabilities

  • Executes SQL queries using valid Supabase authentication tokens.
  • Retrieves detailed metadata about tables, columns, and indexes.
  • Inspects pg_policies to analyze Row Level Security rules.
  • Queries auth.users and related extension tables for access control insights.

Example prompts

  • "Audit the current Row Level Security policies on the 'users' table and summarize any potential over-permissioning risks."
  • "List all database tables and their associated RLS policies, highlighting which ones are currently disabled or missing."
  • "Check if the service role has access to sensitive columns in the 'payments' table and report your findings."

Tips & gotchas

Ensure the AI agent is provided with a valid API key or connection string with appropriate permissions before running audits. This skill relies on the underlying Supabase infrastructure being accessible; it cannot audit projects where network connectivity or authentication credentials are missing.