Suede AI Skills Directory
neon vs supabase-postgres-best-practices
A comparison selected for SQL and Databases, Supabase and Firebase. Compare the task description and license first, then use the score breakdown to inspect their published files.
Quality snapshot: 2026-10-22. Install counts: skills.sh, 2026-11-08. This pair was selected from shared topics and recorded installs; it is not a claim about joint search volume.
At a glance
| Evidence | neon (neondatabase/agent-skills) | supabase-postgres-best-practices (supabase/agent-skills) |
|---|---|---|
| Listing | neon | supabase-postgres-best-practices |
| Task | Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database. | Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query. |
| Quality score | 74/100 · C | 67/100 · D |
| License | Apache-2.0 | MIT |
| Cost lane | free-open-source | free-open-source |
| Recorded installs | 258,711 | 477,325 |
| Report | Score report | Score report |
Where the scores differ
| Component | neon | supabase-postgres-best-practices |
|---|---|---|
| Structural checks | 56 / 56 | 48 / 56 |
| Description length | 1 / 5 | 3 / 5 |
| Boundary clause | 0 / 4 | 0 / 4 |
| Example request | 3 / 3 | 0 / 3 |
| Instruction depth | 1 / 7 | 1 / 7 |
| Reference files | 3 / 3 | 3 / 3 |
| Bundled scripts | 0 / 2 | 0 / 2 |
| Recent maintenance | 9 / 9 | 9 / 9 |
| Curated-list citations | 1 / 7 | 3 / 7 |
| Tool permissions declared | 0 / 2 | 0 / 2 |
| Compatibility declared | 0 / 2 | 0 / 2 |
neon has the higher structural-quality score by 7 points. Use the task descriptions above to judge fit. These scores do not measure runtime performance or security.
Inspect before installing
neon and supabase-postgres-best-practices link to their publishers, licenses and installation routes. Read the source before giving either skill access to your project.