Skills

Prisma Skills: Equip AI Coding Agents with Prisma ORM Database Development Know-How

To have an AI coding agent handle schemas, CLI tasks, and v7 upgrades according to official Prisma practices, install this official skills pack; your agent must support the Agent Skills format, and the ORM skills target Prisma ORM 7.6.x.

Official source · prisma/skills

Install

npx skills add prisma/skills

Who It's For

  • Developers doing Prisma ORM database work inside an AI coding agent: when writing schemas, running the Prisma CLI, or handling other database tasks, you want the agent to come with an officially packaged set of instructions to extend its capabilities.
  • Teams using Prisma ORM 7.6.x, or preparing to upgrade from Prisma 6 to v7 — the repository explicitly states that the ORM-related skills target 7.6.x, and upgrade scenarios should use the prisma-upgrade-v7 skill.
  • When it's not a fit: if your project doesn't use Prisma ORM, these skills have no corresponding capabilities; the evidence doesn't state whether they work with other ORMs or non-database tasks, so don't assume they do.
  • Prerequisites: you need a coding agent that supports Agent Skills (the agentskills.io format), and an environment where npx can run. The evidence doesn't list which specific clients are supported, nor environment requirements such as Node.js versions — these are unknowns.

Your First Try in 3 Minutes

There is only one recommended main path: install with the official npx skills add command.

  1. Prerequisites: Node.js/npm is installed in your environment (so npx works), and your agent supports the Agent Skills format. The evidence doesn't list a supported-client list; if you're unsure whether your agent supports it, confirm first.

  2. Install location: run the install command in your project directory, or wherever your agent prompts for the install location.

  3. Install all skills:

    npx skills add prisma/skills

    If you only want a single skill (e.g., prisma-cli), the official docs also provide a way to install individually, as a secondary option: npx skills add prisma/skills --skill prisma-cli.

  4. Trigger a low-risk task: after installation, the skills are automatically available. The official explanation is "the agent uses them when it detects relevant tasks." For your first try, pick a read-only or diagnostic task — for example, ask the agent to describe the current schema structure of your Prisma project, or explain what the next database step should be. These tasks don't modify files or run commands with side effects.

  5. Success signals: the install command finishes normally, and afterwards the agent follows the skill's instructions when you give it Prisma-related tasks (e.g., answering according to official Prisma workflows or invoking Prisma CLI steps). Note: different text or task types map to different skills; the evidence doesn't describe a unified verification process or evaluation rubric. If your task isn't database-related, the agent may not trigger these skills — that doesn't mean installation failed.

On safety boundaries: npx skills add writes new instruction files to your agent, which is itself a change to your local environment; beyond that, what else the install script does (network access, which paths it writes) is not stated in the evidence and remains unknown. Keep your first task read-only.

Use Cases

Case 1: Have the agent assist with ORM development following official Prisma workflows. Scenario: you're writing a Prisma schema or need to run Prisma CLI commands in a 7.6.x project. How: after completing npx skills add prisma/skills, simply give the agent a task such as "check my Prisma schema and tell me what to do next." The repository states the ORM-related skills target Prisma ORM 7.6.x, and the agent automatically applies the matching skill when it detects a relevant task. Expected outcome: the agent's answers and steps follow official Prisma 7.6.x practices rather than outdated patterns. Note that the evidence doesn't enumerate the specific operations of each ORM skill; what can be confirmed is the level of "the agent uses the relevant skill."

Case 2: Upgrading from Prisma 6 to v7. Scenario: your project is still on Prisma 6 and you're preparing to migrate. How: after installation, give the agent an upgrade task and specify the prisma-upgrade-v7 skill. Expected outcome: the agent assists with the migration following the v7 upgrade process. ⚠️ Side-effect checkpoint: database schema migrations and version upgrades typically modify files, run commands, and may change the database — before doing anything, have the agent present a plan and get your confirmation; the evidence doesn't state which specific commands the skill runs internally, so confirm each one before execution.

Usage Boundaries

  • Files and commands: the installation itself writes skill files; during use, the agent may read/write project files or run Prisma CLI commands — the evidence doesn't state the exact boundaries. Always get explicit confirmation before any file modification or migration-type operation.
  • Network access: npx skills add needs to download the skills; whether the agent has network behavior at runtime is not stated in the evidence and should be treated as unknown.
  • Runtime environment and clients: requires npx and an agent compatible with the Agent Skills format. The official docs don't list specific supported clients, nor OS differences — don't infer from this that your environment will or won't work.
  • Officially stated limitations: the ORM skills target Prisma ORM 7.6.x; Prisma 6 users should use prisma-upgrade-v7. Other versions are not covered in the evidence.
  • Unconfirmed key information: the complete list of skills and each skill's specific behavior, supported language/platform scope, and whether secrets or environment variables are read — none of these have official evidence. If in doubt, consult the repository at https://github.com/prisma/skills before use.