Prisma vs Drizzle vs Supabase: Best Claude DB Skill 2026
A. Frans
Published July 28, 2026
Table of Contents
A database skill does not write your queries. Claude already writes queries. What it stops is the agent inventing a schema that looks plausible and does not exist, then confidently generating twelve files against it.
That is the whole value proposition, and it explains why the three most-installed database skills for Claude Code take completely different routes to the same goal. Prisma ships ORM conventions. Drizzle ships type-safe SQL patterns. Supabase ships a bundle that includes live access to your actual project. Picking wrong means installing something that answers a question you were not asking.
Quick comparison
| Skill | Install | Stars | License | Trust | Type |
|---|---|---|---|---|---|
| Prisma Database | claude skill add prisma/prisma | 47,406 | Apache-2.0 | Verified | Skill |
| Drizzle ORM | claude skill add drizzle-team/drizzle-orm | 35,266 | Apache-2.0 | Verified | Skill |
| Supabase Agent Skills | claude skill add supabase/agent-skills | 2,425 | MIT | Verified | Skill |
| Supabase MCP | claude mcp add supabase -- npx -y @supabase/mcp-server | 2,833 | Apache-2.0 | Official | MCP server |
| Atlas | claude skill add ariga/atlas | 8,609 | Apache-2.0 | Verified | Skill |
| DBHub | claude mcp add dbhub -- npx -y bytebase/dbhub | 3,231 | MIT | Verified | MCP server |
| MCP Toolbox | claude mcp add mcp-toolbox -- npx -y googleapis/mcp-toolbox | 16,023 | Apache-2.0 | Official | MCP server |
| pg-aiguide | claude mcp add pg-aiguide -- npx -y timescale/pg-aiguide | 1,795 | Apache-2.0 | Verified | MCP server |
| Neon Postgres | claude mcp add neon -- npx -y @neondatabase/mcp-server-neon | 619 | Apache-2.0 | Verified | MCP server |
Prisma Database
Repo: github.com/prisma/prisma
claude skill add prisma/prisma
The largest of the three by adoption, and the most opinionated. It teaches Claude the Prisma way of doing things: schema.prisma as the single source of truth, generated client, migration files under version control, relation syntax that Prisma understands.
Where it earns its install is migrations. Ask Claude to add a column to a live Prisma project without this skill and you get a reasonable chance of a hand-edited SQL file that drifts from the schema. With it, you get prisma migrate dev, a properly named migration, and a regenerated client. The agent follows the workflow the tool was designed around instead of improvising.
The cost is that it is Prisma-shaped. On a project using raw SQL or a different ORM, the skill pushes patterns that do not fit and you spend your time arguing with it.
Install if your project already has a schema.prisma. Otherwise skip.
Drizzle ORM
Repo: github.com/drizzle-team/drizzle-orm
claude skill add drizzle-team/drizzle-orm
Drizzle sits closer to SQL, and the skill reflects that. Rather than teaching an abstraction, it teaches how to write typed queries that read like SQL and fail at compile time when your schema changes. For agent-assisted work this is a real structural advantage: type errors are a feedback signal Claude can act on without you in the loop, and Drizzle produces a lot of them at exactly the right moments.
It handles the edge case that trips up most ORMs, complex joins and window functions, without dropping to raw strings and losing the types. Claude writes those correctly with the skill loaded and badly without it, because Drizzle's query builder syntax is dense and easy to half-remember.
The tradeoff runs opposite to Prisma. You get more control and less scaffolding. Migrations through drizzle-kit are lighter but leave more decisions to you, which means more chances for an agent to make one you disagree with.
Install if you are on Drizzle, or if you are choosing an ORM now and want the agent-friendlier of the two.
Supabase Agent Skills and Supabase MCP
Repos: github.com/supabase/agent-skills and github.com/supabase-community/supabase-mcp
claude skill add supabase/agent-skills
claude mcp add supabase -- npx -y @supabase/mcp-server
Supabase ships both halves, and the difference between them is the most useful thing here.
The agent-skills bundle is instructions. It teaches Claude Supabase conventions: row level security policy syntax, auth helper patterns, edge function structure, the storage API. It reads nothing and touches nothing. It is text loaded into context.
The MCP server is a connection. It can list your tables, read your live schema, run queries, and manage your project. That is more capable, and it is why the RLS use case is the one worth installing for. Row level security is where most Supabase projects break, and an agent that can read your existing policies before writing a new one makes materially better decisions than one guessing from the docs.
The MCP server carries your credentials. The skill does not. Those are different risk profiles wearing the same "Supabase support" label.
Install the skill on any Supabase project. Add the MCP server when you want the agent working against the live schema, and read the security section first.
Worth installing alongside
Atlas (8,609 stars) handles declarative migrations as schema-as-code, independent of ORM. It is the answer when your database is shared across services written in different languages and no single ORM owns the schema.
DBHub (3,231 stars) is a token-efficient MCP server covering Postgres, MySQL, and SQL Server. It supports read-only mode, which makes it the safest way to give an agent schema visibility on a database you care about.
MCP Toolbox (16,023 stars, official Google) is the enterprise option, with connection pooling and auth built for production rather than a laptop.
pg-aiguide (1,795 stars) from Timescale serves Postgres documentation and idioms to the agent. Useful specifically for the Postgres features people underuse: partial indexes, CTEs, EXPLAIN output that Claude reads correctly.
Neon Postgres (619 stars) exposes database branching, which pairs unusually well with agent work. Branch, let Claude run migrations against the branch, inspect the result, discard if wrong.
Security: the part that decides this
Every skill here is Apache-2.0 or MIT and marked verified or official in our directory. That is a floor, not a guarantee. Two things deserve a closer look.
An agent skill is instructions loaded into the model's context. Worst case, bad instructions cause the agent to write bad code, which you review before merging. The blast radius is your diff.
An MCP server runs as a process with credentials you provide. Worst case is bigger. It can read data and, depending on configuration, write it. Supabase MCP, DBHub, MCP Toolbox, pg-aiguide, and Neon are all in this category.
Three rules that cost nothing:
Point MCP servers at development databases, not production. If you must connect to production, use read-only mode where the server supports it. DBHub does.
Scope the credentials you hand over. A Supabase service role key bypasses row level security entirely, which is precisely the thing you installed the skill to get right. Use a scoped key.
Read the SKILL.md before installing. All five repos above are open source and the file is short. A skill is instructions to your agent, and you should know what they say.
Anyone doing this daily should also read our roundup for developers and the cybersecurity-professionals list, since the MCP credential question is a security review question more than a tooling one.
Which one
On a Prisma project: the Prisma skill, no debate.
On a Supabase project: the agent-skills bundle first, MCP server second once you have decided on credential scope.
On Drizzle, or choosing fresh: Drizzle. The compile-time errors give an agent a feedback loop that ORM abstractions hide.
On a database no ORM owns: Atlas for migrations, DBHub in read-only mode for visibility.
Installing all three of the main skills at once is the wrong move. They carry conflicting opinions about migrations, and Claude will follow whichever loaded last.
FAQ
Do I need a database skill if Claude already knows SQL? For a one-file script, no. The skills earn their place on an existing codebase, where the failure is not bad SQL but the agent inventing table and column names that sound right. Skills anchor it to your conventions; MCP servers anchor it to your actual schema.
Skill or MCP server, if I only pick one? Skill. It is lower risk, needs no credentials, and fixes the most common failure. Add the MCP server when you specifically need the agent reading live schema.
Can I run Prisma and Drizzle skills together? Technically yes, practically no. They give contradictory migration guidance and you will get inconsistent output depending on context ordering.
Is the Supabase MCP server safe on production? Not with a service role key. That key bypasses row level security. Use a scoped key, or point it at a development project and copy the resulting migrations across yourself.
How do I check a skill before installing? Open the repo, read SKILL.md, check the license, and check the commit history for recent activity. Every skill here is public. For deeper checks, see our guide on auditing agent skills before you install them.
Share this article
⚙Related Tools
📄Related Articles
Get More AI Tool Guides
New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.