Supabase Schema Health Check
For an indie dev onboarding to a new Supabase project (or validating an existing one) who wants a one-prompt health check. Verifies connectivity, inspects tables/columns/constraints, flags drift against an expected schema, optionally applies a migration.
Silent schema drift
Here's what doing this by hand looks like today — and why it doesn't scale.
Schema drift accumulates silently until prod breaks
Nobody runs connectivity or index checks until there's an outage
Dashboard spelunking for a health report wastes a morning
Composio collapses all of this into one prompt — here's what that looks like.
Your agent runs it end-to-end.
- 01Ping the project — confirm status = ACTIVE_HEALTHY
- 02List tables in public schema
- 03For each table, list columns with types, nullability, defaults
- 04Check constraints (PKs, FKs, unique)
- 05Check RLS status
- 06If an expected schema is providedCompute drift: missing tables, missing columns, type mismatches, missing RLS.
- 07Compose a health report
- 08If apply_migration is true and drift is detected, author a DDL migration
Know your DB is healthy
A single prompt returns a health scorecard — connectivity, schema drift, missing indexes — before your users notice.
Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.
Debug a Vercel App End-to-End
Read the logs, reproduce in a browser, patch GitHub, redeploy — all in one session.
Read →Summarize Today's Unread Emails
One prompt turns an inbox of 50+ unread into a 5-bullet digest with the one thing you must answer.
Read →Catch Up on Slack Since Yesterday
Ask "what happened in Slack yesterday?" and get a consolidated, channel-by-channel recap with links back to the threads.
Read →