supabase-audit-tables-list

List Supabase PostgREST API tables with schema, columns, primary keys, and risk levels.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/marvinbiss/servicesartisans --skill supabase-audit-tables-list-marvinbiss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-audit-tables-list
Source: https://github.com/marvinbiss/servicesartisans/tree/main/.cursor/skills/supabase-audit-tables-list
Command: npx skills add https://github.com/marvinbiss/servicesartisans --skill supabase-audit-tables-list-marvinbiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify potential security vulnerabilities by cataloging all database tables exposed through the Supabase PostgREST API, thereby revealing the project's API attack surface.

Core Features & Use Cases

  • API Attack Surface Discovery: Lists all tables accessible via the PostgREST API.
  • Security Auditing: Essential before testing Row Level Security (RLS) policies or performing comprehensive security audits.
  • Data Model Inventory: Provides a clear overview of exposed data models.
  • Use Case: Before conducting a security assessment on a Supabase project, use this skill to get a complete list of all tables that could potentially be accessed or manipulated through the API.

Quick Start

List all tables exposed on my Supabase project.

Frequently Asked Questions about supabase-audit-tables-list

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all tables exposed by the Supabase PostgREST API?

To list tables exposed via the Supabase PostgREST API, you must discover and catalog all accessible database tables. This process details each table's schema, columns, primary keys, and risk levels to map the API attack surface.

What is Supabase API attack surface discovery?

Supabase API attack surface discovery identifies all database tables accessible through the PostgREST API. It catalogs exposed schemas, columns, and primary keys to reveal potential security vulnerabilities before comprehensive security audits.

Do I need a database audit before testing Supabase RLS policies?

Yes, a database audit listing exposed tables is essential before testing Supabase RLS policies. Cataloging the API attack surface identifies accessible data models, ensuring your Row Level Security tests cover all vulnerable endpoints.

How do I inventory exposed data models in Supabase for security auditing?

To inventory exposed data models for security auditing, list all database tables accessible via the Supabase PostgREST API. This provides a clear overview of table schemas, columns, and primary keys, detailing exposed data risk levels.

Can I check which database schemas are accessible through my Supabase API?

You can check accessible database schemas by listing all tables exposed via the Supabase PostgREST API. This discovery process details the schema, columns, and primary keys for each accessible table to assess your attack surface.