Prisma Skills
Prisma skills for agents: Prisma 7 CLI, client API, ORM and Postgres setup, upgrades to Prisma 8 and deploying on Compute.
- 80 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The skills steer an agent to run migrations and commands that change the schema and can wipe database data.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/prisma-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills steer an agent to run migrations and commands that change the schema and can wipe database data.
This is third-party code. Review the repository files before installing.
What it does
The collection from Prisma itself teaches an agent to work with Prisma ORM, Prisma Postgres and Prisma Compute. `prisma-cli` describes ORM 7 commands: `init`, `generate`, `migrate dev`, `migrate deploy`, `db push`, `db pull`, `db seed`, `studio`. `prisma-client-api` covers Prisma Client queries, filters, transactions and raw SQL. `prisma-orm-setup` and `prisma-postgres-setup` connect the ORM and a database and verify a query. Separate skills drive upgrades: `prisma-upgrade-v7` from version 6 to 7, `prisma-postgres-upgrade` straight to Prisma 8, and `prisma-mongodb-upgrade`, which explains why MongoDB projects have no path to 7 and helps choose between staying on 6 and migrating. `prisma-driver-adapter-implementation` is for people writing a SQL adapter, and `prisma-compute` covers app deployment.
Who it is for. TypeScript developers with Prisma who upgrade the ORM version, set up a database or deploy an app with an agent.
Good fit when
- A Prisma 6 project is moved to version 7 with ESM and `prisma.config.ts` taken into account.
- A PostgreSQL app on ORM 6 or 7 is upgraded to Prisma 8 in one pass.
- A new Prisma Postgres database is created and verified with a query from the app.
- An agent writes queries with `select`, `include` and transactions through `$transaction`.
Not a fit when
- The project does not use Prisma.
- You need to move MongoDB to Prisma 7, for which no path exists.
- You work on an old Prisma version you do not plan to change.
Example request
Upgrade this project from Prisma 6 to Prisma 8 with the prisma-postgres-upgrade skill and verify that queries return the same data.Limitations
The skills are version-bound: they describe Prisma ORM 7 and 8 and keep apps on 6 and 7 on their version. For the PostgreSQL upgrade to Prisma 8 exact versions are given, not `@latest`. The `prisma-database-setup` skill is deprecated and redirects to `prisma-orm-setup`. The skills change schema and migrations, and commands such as `migrate reset` erase data, so run them on a database copy. Deploying on Prisma Compute requires Prisma 8. For MongoDB on Prisma 6 the collection gives a decision table and signs when migration is not advised.
How to disable. Remove the skills with the manager (`npx skills list` shows what is installed) or by hand from the agent skills directory.
FAQ
How do I install all the skills?
Run `npx skills add prisma/skills`. A single skill installs with the `--skill` flag, for example `--skill prisma-cli`, and `--list` prints what is available.
How does prisma-upgrade-v7 differ from prisma-postgres-upgrade?
The first moves a project from version 6 to 7 and covers breaking changes. The second takes a PostgreSQL app on ORM 6 or 7 straight to Prisma 8.
Can MongoDB be upgraded to Prisma 7?
No: MongoDB on version 6 has no path to 7 because 7 has no connector. The `prisma-mongodb-upgrade` skill helps choose between staying on 6 and migrating to Prisma 8.
Do I need to enable the skills manually?
No, once installed the agent picks the right skill when it sees a Prisma task.
What does prisma-compute do?
It covers deploying an app on Prisma Compute. An app on ORM 6 or 7 first needs a move to Prisma 8.
Discussion
No questions or reviews yet.
Related
SkillsPrisma 8 skill
prisma-8
The official Prisma 8 skill installed from your project's packages: data contract, migrations, queries and version upgrades
Two official Prisma MCP servers: a local one for migrations and Prisma Studio, and a remote one for managing Prisma Postgres databases
Supabase's official skills: help an agent work with the database, Auth, Edge Functions and Postgres best practices
Official MongoDB skills for natural-language queries, schema design, indexing, Atlas Search and driver connection setup
Sixteen Spring Boot skills: the agent explores the application first, then edits JPA, DTOs, REST, Security, Kafka and tests.
The Elysia v2 skill teaches an agent to build, debug and migrate Elysia backends: validation, plugins, typed clients, deploy
README in short
The README lists the skills with descriptions, use cases and topics, then installation of all or selected skills, listing available and installed ones and sample requests to an agent.
README badge
Original SKILL.md
--- name: prisma-cli description: Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI. license: MIT metadata: author: prisma version: "7.9.1" --- # Prisma ORM 7 CLI reference These commands and examples apply to **Prisma ORM 7** only. For setup, connection repair, or a Prisma 8 application, load [prisma-orm-setup](../prisma-orm-setup/SKILL.md). Use the project's version-matched CLI. Do not install a floating `prisma@latest` to run these commands. ## Boundary: Platform and Compute Do not confuse the stable ORM command (`prisma`) with the public-beta Platform package (`@prisma/cli`, binary `prisma-cli`). Use `prisma-compute` for Compute apps and workspace auth, and `prisma-postgres-setup` for Platform projects and databases. ## When to Apply Reference this skill when: - Setting up an explicitly selected Prisma 7 project (`prisma init`) - Generating Prisma Client (`prisma generate`) - Running database migrations (`prisma migrate`) - Managing database state (`prisma db push/pull`) - Using local development database (`prisma dev`) - Debugging Prisma issues (`prisma debug`) - Generating shell completions (`prisma complete`) ## Rule Categories by Priority | Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Setup | HIGH | `init` | | 2 | Generation | HIGH | `generate` | | 3 | Development | HIGH | `dev` | | 4 | Database | HIGH | `db-` | | 5 | Migrations | CRITICAL | `migrate-` | | 6 | Utility | MEDIUM | `complete`, `studio`, `validate`, `format`, `debug`, `mcp` | ## Command Categories | Category | Commands | Purpose | |----------|----------|---------|