Prisma SQL Driver Adapter Implementation
Reference for implementing Prisma ORM 7 SQL driver adapters — contract, transactions, savepoints, error mapping
- What
- Reference for implementing Prisma ORM 7 SQL driver adapters — contract, transactions, savepoints, error mapping
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Prisma team's required reference for anyone implementing or modifying a SQL driver adapter: it lays out the full contract (`SqlDriverAdapterFactory`, `SqlMigrationAwareDriverAdapterFactory`, `SqlDriverAdapter`, `Transaction`) with the priority rules that keep adapters safe — one dedicated connection per transaction (never shared adapter-global depth), `commit`/`rollback` as lifecycle cleanup hooks rather than a second SQL commit, savepoints living on the `Transaction` object (optional, only where the provider supports them), and original database error code/message preservation so unmapped failures surface as useful `P2039` errors. It goes deep on value mapping (arg types respected, 64-bit integers without JS truncation, decimal to `Numeric`, binary to `Bytes`, dates to their explicit types, unsupported natives to `DriverAdapterError`), provider-aware `executeScript` (never naive `;` splitting — it breaks functions, triggers, and quoted strings), factory ownership and `dispose()` semantics, isolated shadow databases for migrations (never pointed at the primary), and a verification checklist from typecheck against the exact `@prisma/driver-adapter-utils` version to concurrent-transaction and dispose-ownership tests. By @prisma, listed here with credit to its creator. Honest caveats: this is protocol-boundary engineering — type-compatible code can still corrupt values, leak connections, or break transactions, and this guide is for adapter authors, not application developers; always work against the exact `@prisma/driver-adapter-utils` version installed by the target Prisma release. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Prisma SQL Driver Adapter Implementation is a free Muse skill that gives your Muse the required reference for implementing or modifying a Prisma ORM 7 SQL driver adapter, laying out the full contract with priority rules that keep adapters safe, including one dedicated connection per transaction, savepoints on the transaction object, and original database error preservation.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit be16a87Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Muse account with skill installation enabled Install "Prisma SQL Driver Adapter Implementation" for me. Reference for implementing Prisma ORM 7 SQL driver adapters — contract, transactions, savepoints, error mapping Repository: https://raw.githubusercontent.com/prisma/skills/be16a8740d01363d13552b317042431ee8dfc581/prisma-driver-adapter-implementation/SKILL.md Pinned version: install the code at commit be16a8740d01363d13552b317042431ee8dfc581 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "prisma-driver-adapter-implementation". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- be16a87 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.