Question 1

What is the Prisma skills pack and what ships in it?

Accepted Answer

It's the official set of nine agent skills from prisma/skills covering the ORM and the platform: prisma-cli (command reference), prisma-client-api (query API), prisma-database-setup (per-provider config), prisma-upgrade-v7 (v6→v7 migration), prisma-mongodb-upgrade (MongoDB decision path), prisma-postgres and prisma-postgres-setup (Prisma Postgres platform), prisma-compute (app deployment), and prisma-driver-adapter-implementation (custom driver adapters). All follow the Agent Skills format and install with npx skills add.

Question 2

Why do all nine skills show nearly identical install counts?

Accepted Answer

Because they're one pack counted nine times. On the 2026-09-01 skills.sh scrape, the nine ranged from 235,757 (prisma-mongodb-upgrade) to 253,040 (prisma-database-setup) — a 17K spread across the whole set, with lockstep weekly curves: prisma-cli at [43,794, 41,486, 39,813, 20,907] and prisma-compute at [43,410, 41,201, 39,452, 20,586], four weeks of matching waves. The same pack-counter signature shows up in azure-skills (nine skills, 235–499K, identical wave shapes). Treat the totals as 'the pack is installed a lot', not as per-skill usage heat.

Question 3

Is prisma-cli the ORM skill or the Platform CLI skill?

Accepted Answer

The ORM one — and the SKILL.md carries an explicit boundary warning about the mix-up. The stable ORM command is `prisma` (this skill, version 7.9.1). The public-beta Platform package is `@prisma/cli` with binary `prisma-cli`, routed to the prisma-compute skill. The file spells it out: use prisma-compute for Compute apps and workspace auth, prisma-postgres for Platform projects and databases, and this skill for ORM commands like init, generate, migrate, db push/pull, dev, debug, and studio.

Question 4

What actually breaks when upgrading Prisma to v7?

Accepted Answer

Four headline changes per prisma-upgrade-v7 (v7.6.0): the generator moves to `prisma-client` with required output paths and generated entrypoints (client, browser, models, enums), driver adapters become mandatory for SQL providers, config moves to prisma.config.ts with explicit environment loading, and the module system goes ESM-first with a CommonJS fallback via moduleFormat = 'cjs'. It also lists removed features — middleware, metrics, and legacy CLI behavior — plus a special section for Accelerate users. The skill's crash case is import errors right after upgrade, which trace back to the new generated entrypoints.

Question 5

Does the v7 upgrade guide apply to MongoDB projects?

Accepted Answer

No, and the skill says so on the first page: 'Using MongoDB? This guide does not apply.' Prisma v7 has no MongoDB connector, so prisma-mongodb-upgrade exists as a separate decision and migration skill. It lays out the landscape — v6 is terminal for MongoDB, v7 has no path, Prisma Next is the successor — with a stay-on-v6 vs migrate-now decision table, schema/contract and client API mapping, and a cutover checklist with no-go signals. If an agent proposes an 'upgrade MongoDB to v7' plan, that plan is wrong out of the box.

Question 6

What runtime prerequisites do the skills assume?

Accepted Answer

prisma-database-setup pins Node.js 20.19.0+ and TypeScript 5.4.0+, with provider guides for PostgreSQL, MySQL, SQLite, SQL Server, MongoDB, and CockroachDB. The file has one Bun-specific rule worth stealing: run CLI commands with `bunx --bun prisma` so Prisma uses the Bun runtime instead of silently falling back to Node. The client-api skill (v7.9.1) organizes its reference by priority — model queries, transactions, and raw SQL are CRITICAL; client construction, query shape, filters, and relations are HIGH.

Question 7

Which skill should I install first?

Accepted Answer

prisma-cli, then prisma-database-setup — that pair covers the daily loop: init, generate, migrate, db operations, plus per-provider config and connection-string troubleshooting. Add prisma-client-api when your agent writes real queries, prisma-upgrade-v7 the week you plan a v6→v7 migration, and prisma-mongodb-upgrade if MongoDB is in the mix. Skip prisma-compute and the two prisma-postgres platform skills unless you're deploying Compute apps or using Prisma Postgres — they cover paid platform workflows, not the ORM.

Question 8

What does the postgres platform skill cover that database-setup doesn't?

Accepted Answer

prisma-postgres (v7.9.1) is about the hosted product: provisioning instant databases with a create-db CLI (flags include --ttl, --copy, --quiet, --open), linking local projects with `prisma postgres link`, managing resources through the Management API or its typed SDK, and connection choices between direct TCP and serverless drivers. prisma-database-setup stays in ORM-land — provider strings, env-var configuration, and client instantiation. The boundary is the same flavour as cli-vs-compute: platform vs ORM, and the pack keeps the two deliberately separate.

Prisma on Top AI Skills

I Ran npx create-db and Got a Live Postgres in Seconds

Prisma Skills Pack FAQ: Nine Agent Skills, One ORM

Frequently Asked Questions

Why a Prisma Skills Pack FAQ Exists

Prisma on Top AI Skills

I Ran npx create-db and Got a Live Postgres in Seconds

One Command, Zero Signup

Prisma Skills Pack FAQ: Nine Agent Skills, One ORM

Frequently Asked Questions

Why a Prisma Skills Pack FAQ Exists