Supabase Report Compare
CheckedCompares Supabase report data across time periods, highlighting key changes and trends in your database.
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-report-compare -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, 340 lines
About this skill
The supabase-report-compare skill enables AI agents to analyze and contrast Supabase database reports, identifying discrepancies in data structures or query results between different environments or snapshots. It streamlines the validation of database migrations and security configurations by automatically highlighting changes across datasets.
When to use it
- Validating that production database schemas match development versions after a migration deployment.
- Comparing audit logs from two different Supabase projects to detect unauthorized access patterns.
- Identifying data drift between staging and live environments before rolling out new features.
- Verifying that row-level security policies produce consistent results across multiple test datasets.
Key capabilities
- Ingests and parses raw Supabase report exports or query outputs.
- Performs side-by-side comparison of table schemas, column definitions, and data values.
- Generates a structured summary of differences, including added, removed, or modified fields.
- Supports complex join comparisons across multiple related tables within the dataset.
Example prompts
- "Compare the user authentication logs from my staging Supabase project against production and list any new failed login attempts."
- "Analyze the difference between these two exported report files to find which columns were added in the latest migration."
- "Run a comparison on the
orderstable data from last month versus this month to identify sudden volume spikes or anomalies."
Tips & gotchas
Ensure both reports being compared originate from compatible Supabase versions to avoid false positives caused by schema versioning differences. For large datasets, consider filtering the input to specific date ranges or ID subsets to keep processing times manageable and results focused.