← Search

Prisma Compute Deployment Guide
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit ba3f9d7
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: Prisma Compute is a paid cloud service: you need a…

Prisma Compute Deployment Guide

Prisma Compute deployment guide — Composer 2.0.0, module.ts, prisma deploy/dev, stages, service logs

At a glance
What
Prisma Compute deployment guide — Composer 2.0.0, module.ts, prisma deploy/dev, stages, service logs
Cost
Free
Needs
Prisma Compute is a paid cloud service: you need a Prisma account and workspace to deploy. Deploying uses the Prisma 8 CLI (`npx prisma`, published identically as `@prisma/cli`); in a Prisma 6 or 7 project, `npx prisma` runs that version's ORM CLI, which has none of these commands. No key is needed to install the skill itself: installing it is only Markdown files, nothing runs and nothing is sent during installation.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Prisma Compute Deployment Guide is a free Muse skill that guides your Muse through creating, deploying, and operating apps on Prisma Compute, covering the right CLI surface, a typed prisma.compute.ts deploy config, framework deploy readiness, authentication, and logs, plus runtime rules that bite in production like binding 0.0.0.0 and listening on PORT.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit ba3f9d7

Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: Prisma Compute is a paid cloud service: you need a Prisma account and workspace to deploy. Deploying uses the Prisma 8 CLI (`npx prisma`, published identically as `@prisma/cli`); in a Prisma 6 or 7 project, `npx prisma` runs that version's ORM CLI, which has none of these commands. No key is needed to install the skill itself: installing it is only Markdown files, nothing runs and nothing is sent during installation. Install "Prisma Compute" for me. It is the deploy-and-operate playbook for Prisma Compute: every deploy goes through a Prisma Composer app (a `module.ts` root module, one `service.ts` per server declared with `compute()`) and the Prisma 8 CLI: `prisma deploy` / `prisma dev`, preview stages, deploy on push, service logs, versions, rollback, env vars and custom domains. Source: https://raw.githubusercontent.com/prisma/skills/ba3f9d73200bbb62e49733ab93a961fd138a2c18/prisma-compute/SKILL.md (the skill is the whole prisma-compute/ folder at that commit: SKILL.md plus its references/ folder of 10 files) Pinned version: install the code at commit ba3f9d73200bbb62e49733ab93a961fd138a2c18 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 17, 2026: Skill Harbor regenerated this install prompt from the current upstream file. What changed since the version the previous prompt described: the skill is now version 2.0.0, a breaking rewrite. The pre-Composer Compute CLI is gone: `@prisma/cli app deploy`, `prisma.compute.ts` / `defineComputeConfig` and `compute:deploy` now fail, their config files are not read and their environment variables are ignored. Deploys now go through a Composer app (a `module.ts` root module, a `composer` section in `prisma.config.ts`) with the Prisma 8 CLI: `prisma deploy module.ts` to deploy, `prisma dev module.ts` to run locally, `service logs` and `service version` for operations. The previous prompt described the removed CLI; following it now fails. 1. Download the whole prisma-compute/ folder at the pinned commit (SKILL.md and every file under references/) into a temporary folder. 2. Compare SKILL.md with the fingerprint from Skill Harbor's review of 2026-10-17: - SKILL.md: SHA-256 ce27e7ac6f7072187b1883ebf2bc8981d565c3e2bdb23887483c91195e2c8869 If it does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 3. Read SKILL.md and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm these points from the file: - The removed-surface table: the old commands fail (`CLI.UNKNOWN_COMMAND`), and a project still carrying `prisma.compute.ts` or a `compute:deploy` script must be ported to Composer instead of running them. - Production intent: a deploy without `--stage`, and a push to the connected default branch, change production, so my go-ahead comes first; previews use `--stage <name>`. - Credentials that some commands print once (`postgres create`, `bucket key create`, connection creation) are stored, never echoed; env var values are write-only through `project env`. - The installed packages ship their own version-matched skills (`npx prisma skills sync`); this skill covers the deploy and operations workflow. Nothing is sent anywhere during installation itself. 4. When I say yes, copy the whole folder's contents into my skills folder, in a folder named "prisma-compute". 5. Check the copy with no network calls (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do (for example: log in once with `npx prisma auth login`, and port any project still using the removed CLI to Composer before deploying). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me. Never print or paste a secret value.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit ba3f9d7 · 2026-10-17
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
ba3f9d7 · 2026-10-17
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.