A self-updating vector-database skill: it fetches current Qdrant guidance at run time instead of shipping a snapshot that rots.
By use case
Top Databases & Schemas Skills
PlanetScale workflows, schema design conventions, query patterns, migrations.
14 skills indexed · ranked by composite score · updated August 19, 2026
Top 6 Databases skills
- 1.qdrant-advisor—A self-updating vector-database skill: it fetches current Qdrant guidance at run time instead of shipping a snapshot that rots.
A self-updating vector-database skill: it fetches current Qdrant guidance at run time instead of shipping a snapshot that rots.
- 2.dbhub—One skill across Postgres, MySQL, SQL Server, MariaDB and SQLite — and its actual job is forcing explore-before-query on real schemas.
One skill across Postgres, MySQL, SQL Server, MariaDB and SQLite — and its actual job is forcing explore-before-query on real schemas.
- 3.supabase-skill—Supabase done right. RLS policies, edge functions, realtime, auth — in idiomatic patterns.
Supabase done right. RLS policies, edge functions, realtime, auth — in idiomatic patterns.
- 4.neon-postgres—Neon serverless Postgres done right — branching, pooling, and scale-to-zero, from Neon.
Neon serverless Postgres done right — branching, pooling, and scale-to-zero, from Neon.
- 5.postgres—The generalist Postgres skill the ecosystem was missing — schema, indexing, extensions and migrations, from a Postgres company.
The generalist Postgres skill the ecosystem was missing — schema, indexing, extensions and migrations, from a Postgres company.
- 6.postgres-database-migration—Zero-downtime Postgres migrations, with the locking behaviour spelled out — which ALTER TABLE takes an AccessExclusiveLock and what to do instead.
Zero-downtime Postgres migrations, with the locking behaviour spelled out — which ALTER TABLE takes an AccessExclusiveLock and what to do instead.
About Databases & Schemas
The best agent skills for databases and schemas in 2026 handle safe migrations as well as design — flagging the NOT NULL footgun on large tables, estimating online index build impact on write-heavy loads, and covering Drizzle and Prisma ORM patterns alongside raw Postgres, MySQL, and SQLite DDL. Database & schema Skills give agents the structured workflow needed to design tables, write migrations, optimize queries, and avoid the classic footguns — N+1 queries, missing indexes, lock contention, schema drift between environments. The category covers Postgres, MySQL, PlanetScale, Supabase, SQLite, Mongo, and the increasingly common Drizzle / Prisma ORM patterns.
Common workflows include designing a schema for a new feature, writing a safe migration (NOT NULL adds, large backfills, online index builds), optimizing a slow query with EXPLAIN ANALYZE, generating an ER diagram from an existing schema, designing partitioning strategies for large tables, and reviewing migrations for safety before merge. Several Skills pair with Supabase, PlanetScale, Neon or Snowflake MCP servers for live schema inspection.
Backend engineers, data platform engineers, and product engineers shipping schema changes use these. Composite scoring weights provenance, install count, and how well the Skill handles migrations specifically — the highest-risk part of any database workflow. Skills that flag dangerous migration patterns (NOT NULL without default on large tables, online index build estimates) rank above those that just generate SQL.
Ranked by score
Best Databases Skills
Skills that do databases well — ranked transparently.
One skill across Postgres, MySQL, SQL Server, MariaDB and SQLite — and its actual job is forcing explore-before-query on real schemas.
Supabase done right. RLS policies, edge functions, realtime, auth — in idiomatic patterns.
Neon serverless Postgres done right — branching, pooling, and scale-to-zero, from Neon.
The generalist Postgres skill the ecosystem was missing — schema, indexing, extensions and migrations, from a Postgres company.
Zero-downtime Postgres migrations, with the locking behaviour spelled out — which ALTER TABLE takes an AccessExclusiveLock and what to do instead.
Schema design decisions made explicitly: data types, key strategy, JSONB versus columns, and when partitioning earns its complexity.
PlanetScale's schema branching and index-aware queries, packaged for agents.
Prisma migrations and queries by the book. Index-aware, migration-safe, type-correct.
Caching without the bugs. Invalidation, write-through, cache-aside, distributed locks.
The SQLite slot, filled by Turso — and unusually, a skill that actively steers the agent off the stale API surface web search returns.
The vector-database skill that ships executable scripts rather than prose — the agent runs the query instead of describing it.
MongoDB aggregations and indexing without the foot-guns.
In-process analytical SQL over CSV, Parquet, and Excel — no warehouse, no server.
FAQ
Frequently asked
Postgres, MySQL or SQLite?
The schema-design patterns largely overlap. Migration safety and operational concerns diverge sharply — Postgres has online DDL for most operations, MySQL's online DDL is narrower, SQLite mostly rewrites the table. The top Skills warn about platform-specific footguns.
Can these Skills run migrations?
They generate and review; whether the agent runs them depends on the agent and your approval. Claude Code with a Postgres MCP server can; Claude.ai web only generates.
How do they handle ORM-specific patterns?
Drizzle and Prisma have dedicated Skills that produce idiomatic schema definitions and migrations. Generic SQL Skills fall back to raw DDL.
Are these Skills useful for query optimization?
Yes — they read EXPLAIN ANALYZE output and propose index, query-shape, or schema changes. The cloud-native data warehouse Skills (BigQuery, Snowflake) are particularly useful here.
Do they catch unsafe migrations?
The top Skills flag the well-known footguns — NOT NULL on a large table without a default, multi-step migrations that need separate deploys, online index build assumptions on a write-heavy table.
Go deeper
Guides and comparisons for Databases
Ranked recommendations with the reasoning, per-agent compatibility cuts, and head-to-head verdicts.
- Best agent Skills for databases →
The best agent Skills for database work — vendor-published skills for Supabase/Postgres and PlanetScale/MySQL, plus Prisma ORM, MongoDB, and Redis caching patterns.
- Top Databases & Schemas Skills for Cursor →
The 6 databases agent Skills with verified Cursor compatibility, ranked by composite score, with the install command for Cursor and what is not verified there yet.
- supabase-skill vs planetscale-skills →
supabase-skill for Postgres with row-level security, auth, and realtime; planetscale-skills for MySQL with Git-style schema branching at scale.
- postgres vs supabase-skill →
The postgres skill for engine-level decisions — types, indexes, partitioning, extensions; supabase-skill for the platform layer — row-level security, auth, realtime.
Other categories