Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Evidence

Listed
yoanbernabeu·vlatest·database

Retrieves structured data and evidence from Supabase databases based on natural language queries.

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-evidence -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 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: abc123.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

    abc123.supabase.coundeclared

    What it found

    • skills/evidence/supabase-evidence/SKILL.md:158contacts abc123.supabase.co
      "curl_command": "curl -X GET 'https://abc123.supabase.co/rest/v1/users?select=*&limit=5' -H 'apikey: eyJ...' -H 'Authorization: Bearer eyJ...'"
  • 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.

Scanned
1 file, 360 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-evidence skill enables AI agents to interact with Supabase's Evidence API, allowing for the retrieval and management of audit logs and security records. It facilitates deep inspection of database activities and authentication events directly within an agent's workflow.

When to use it

  • Investigating unauthorized access attempts or suspicious login patterns in a production environment.
  • Generating compliance reports by extracting historical data change logs from Supabase tables.
  • Validating the integrity of security policies after deploying new Row Level Security (RLS) rules.
  • Troubleshooting complex query failures by analyzing specific execution traces stored as evidence.

Key capabilities

  • Querying detailed audit trails for database operations and user actions.
  • Filtering evidence records based on timestamps, user IDs, or table names.
  • Exporting structured security logs for external analysis or reporting tools.

Example prompts

  • "Retrieve all failed login attempts for the 'admin' role from the last 24 hours."
  • "List every record modified in the users table by a specific IP address over the past week."
  • "Summarize the security events related to the payments schema that occurred during yesterday's maintenance window."

Tips & gotchas

Ensure your AI agent has appropriate API keys with read permissions for the Evidence endpoint before attempting queries. Be mindful of data retention policies, as older evidence may be automatically purged by Supabase depending on your project settings.