Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Audit Auth Config

Checked
yoanbernabeu·vlatest·database

Helps with Supabase, auditing, authentication 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-auth-config -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-auth-config/SKILL.md
Scanned
1 file, 416 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

What it does

This skill analyzes the authentication configuration of a Supabase project to identify potential security vulnerabilities. It examines settings related to user registration, login, password recovery, and enabled authentication providers (email, phone, OAuth). Crucially, this skill requires progressive file updates during execution – findings must be written to context files (.sb-pentest-context.json) and audit logs (.sb-pentest-audit.log) immediately after each setting is analyzed, not at the end of the process.

When to use it

  • To review authentication security settings before deploying a Supabase project to production.
  • As part of an auditing workflow for auth-related vulnerabilities.
  • During comprehensive security reviews of a Supabase application.
  • To verify specific configuration details, such as whether signup is open and which providers are enabled.

Key capabilities

  • Analyzes Supabase authentication settings via the /auth/v1/* endpoints.
  • Detects if email authentication is enabled by attempting user registration.
  • Checks for phone authentication enablement through settings inspection.
  • Identifies configured OAuth providers by examining settings.
  • Determines if signup is disabled by attempting a signup process.
  • Evaluates email confirmation requirements based on signup responses.
  • Assesses password complexity rules via error message analysis.

Example prompts

  • "Audit authentication configuration"
  • "Check if signup is open and what providers are enabled"

Tips & gotchas

  • Critical: The skill requires progressive file updates to .sb-pentest-context.json and .sb-pentest-audit.log. Do not wait until the end of the process; update these files immediately after analyzing each setting. Failure to do so can lead to data loss if the skill is interrupted.
  • You need a Supabase URL and anon key available for this skill to function correctly.
  • A prior detection step must be completed before running the audit.