Skills prisma-compute
📦

prisma-compute

v1.4.1 Content revision r2 High Risk 🌐 Network access🔑 Env variables📁 Filesystem access⚙️ External commands

Deploy Prisma Apps on Compute

Prisma Compute deployments require correct framework, environment, and authentication settings. This skill guides configuration, deployment, verification, and troubleshooting across supported TypeScript frameworks.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "prisma-compute" from https://skillstore.io/skills/prisma-prisma-compute.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-compute/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/prisma-prisma-compute.md Signed manifest GET /api/skills/prisma-prisma-compute/manifest Signed lockfile GET /api/skills/prisma-prisma-compute/lockfile

Test it

Using "prisma-compute". Check my Hono API before deploying to Compute.

Expected outcome:

Readiness report: Hono target detected. Verify the server entrypoint, all-interface binding, deployed port, environment source, and authentication context before deployment.

Using "prisma-compute". My production deployment succeeded, but its public URL times out.

Expected outcome:

Troubleshooting result: inspect runtime logs, compare configured and listening ports, and confirm the server is not bound only to loopback.

Using "prisma-compute". Plan preview deployments for the web and API packages in my monorepo.

Expected outcome:

Delivery plan: define separate targets, align branch-scoped environments, build each artifact, deploy unpromoted candidates, verify public endpoints, then promote approved releases.

Security Audit

High Risk
v7 • 7/23/2026 Open versioned report

No prompt injection or malicious collection endpoint was found; most static matches are Markdown or deployment documentation. The skill still handles secret-bearing environment files, executes mutable package versions, and documents non-interactive production mutations.

7
Files scanned
1,901
Lines analyzed
16
Review items
0
False positives ignored

Confirmed security concerns (43)

High
references/app-deploy-cli.md:148
Environment file access
bunx @prisma/cli@latest project env add --file .env --role production
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:149
Environment file access
bunx @prisma/cli@latest project env add --file .env.preview --role preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:151
Environment file access
bunx @prisma/cli@latest project env update --file .env --role production
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:157
Environment file access
`app deploy --env .env` loads environment variables from a file for the deployment. A config-backed
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:247
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:263
Environment file access
--env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:281
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:292
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
Show all 43 confirmed findings
High
references/app-deploy-cli.md:303
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:317
Environment file access
--env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:329
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/app-deploy-cli.md:337
Environment file access
bunx @prisma/cli@latest app deploy api --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/compute-config.md:47
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/compute-config.md:83
Environment file access
file: [".env", ".env.production"],
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/compute-config.md:141
Environment file access
env: "apps/web/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/compute-config.md:149
Environment file access
file: "apps/api/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/compute-config.md:83
Environment variant files
file: [".env", ".env.production"],
The configuration explicitly loads .env and .env.production files. These variants commonly contain deployment secrets and therefore require deliberate scope and repository controls.
High
references/create-prisma.md:65
Environment file access
- a `.env` file containing `DATABASE_URL`
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/create-prisma.md:66
Environment file access
- an initial Compute deployment with env vars loaded from `.env`
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:80
Environment file access
bunx @prisma/cli@latest app deploy --framework nextjs --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:107
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:118
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:144
Environment file access
bunx @prisma/cli@latest app deploy --framework nestjs --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:153
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:178
Environment file access
bunx @prisma/cli@latest app deploy --framework tanstack-start --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:222
Environment file access
bunx @prisma/cli@latest app deploy --framework nuxt --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:231
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:243
Environment file access
bunx @prisma/cli@latest app deploy --framework astro --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:253
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:280
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:313
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:359
Environment file access
env: "packages/db/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/frameworks.md:379
Environment file access
--env packages/db/.env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/sdk-api.md:126
Environment file access
bunx @prisma/cli@latest project env add --file .env.preview --branch feature/foo
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/troubleshooting.md:22
Environment file access
test -f .env && sed -n 's/=.*/=<redacted>/p' .env
The command reads a local .env file and prints variable names while redacting values. Redaction reduces exposure, but access to a secret-bearing file is real.
High
references/troubleshooting.md:153
Environment file access
bunx @prisma/cli@latest app deploy --json --no-interactive --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/troubleshooting.md:197
Environment file access
1. Put a real production-ready `DATABASE_URL` in `.env` or project env.
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/troubleshooting.md:200
Environment file access
4. Redeploy with `--env .env` or project env configured.
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/troubleshooting.md:389
Environment file access
bunx @prisma/cli@latest app deploy --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
references/troubleshooting.md:390
Environment file access
bunx @prisma/cli@latest app deploy --branch feature/foo --env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
SKILL.md:148
Environment file access
- `env-deploy-loads-dotenv` - Generated deploy scripts may load env via `prisma.compute.ts` or `--en
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
High
SKILL.md:18-25references/create-prisma.md:11-16
Unpinned Remote Package Execution
Commands repeatedly execute @prisma/cli@latest and create-prisma@latest through package runners. A compromised or unexpectedly changed release would execute with the agent's local privileges.
The cited commands explicitly use the mutable latest tag with bunx. Package runners download and execute that resolved release.
High
SKILL.md:157-164references/app-deploy-cli.md:351-359
Production Mutation Confirmation Bypass
The skill documents production deploy, promotion, rollback, removal, and other remote mutations with non-interactive confirmation flags. Incorrect target inference could alter live infrastructure.
The cited guidance explicitly combines production operations with --yes. Intent guardrails are present, but the commands bypass interactive confirmation once run.
Capability review items (16)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
references/app-deploy-cli.md:150
Database connection strings
bunx @prisma/cli@latest project env add DATABASE_URL=postgresql://... --branch feature/foo
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
High
references/app-deploy-cli.md:152
Database connection strings
bunx @prisma/cli@latest project env update DATABASE_URL=postgresql://... --branch feature/foo
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
High
references/app-deploy-cli.md:165
Database connection strings
- Existing database env values supplied through `--env DATABASE_URL=...`, `--env DIRECT_URL=...`, an
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
High
references/create-prisma.md:65
Database connection strings
- a `.env` file containing `DATABASE_URL`
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
High
references/sdk-api.md:47
Database connection strings
const databaseUrl = process.env.DATABASE_URL
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
High
references/sdk-api.md:48
Database connection strings
if (!databaseUrl) throw new Error("DATABASE_URL is required")
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
High
references/sdk-api.md:58
Database connection strings
envVars: { DATABASE_URL: databaseUrl },
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
High
references/troubleshooting.md:197
Database connection strings
1. Put a real production-ready `DATABASE_URL` in `.env` or project env.
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
Medium
references/compute-config.md:141
Hidden file access
env: "apps/web/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
Medium
references/compute-config.md:149
Hidden file access
file: "apps/api/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
Medium
references/frameworks.md:359
Hidden file access
env: "packages/db/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
Medium
references/frameworks.md:379
Hidden file access
--env packages/db/.env
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
Medium
references/sdk-api.md:35
Environment variable access (dot notation)
token: process.env.PRISMA_API_TOKEN,
The SDK example reads PRISMA_API_TOKEN from the process environment and supplies it to an authenticated client. This is legitimate secret access that requires redaction and least privilege.
Medium
references/sdk-api.md:47
Environment variable access (dot notation)
const databaseUrl = process.env.DATABASE_URL
The SDK example reads DATABASE_URL from the process environment before deployment. This is legitimate credential handling, but accidental logging or broad process access could expose it.
Medium
references/sdk-api.md:35
Environment variable object
token: process.env.PRISMA_API_TOKEN,
The SDK example reads PRISMA_API_TOKEN from the process environment and supplies it to an authenticated client. This is legitimate secret access that requires redaction and least privilege.
Medium
references/sdk-api.md:47
Environment variable object
const databaseUrl = process.env.DATABASE_URL
The SDK example reads DATABASE_URL from the process environment before deployment. This is legitimate credential handling, but accidental logging or broad process access could expose it.

Risk Factors

🌐 Network access (6)
references/app-deploy-cli.md:269 references/frameworks.md:296 references/troubleshooting.md:350 references/troubleshooting.md:351 SKILL.md:3 SKILL.md:128
🔑 Env variables (40)
references/app-deploy-cli.md:150 references/app-deploy-cli.md:152 references/app-deploy-cli.md:165 references/app-deploy-cli.md:195 references/compute-config.md:92 references/create-prisma.md:107 references/create-prisma.md:65 references/create-prisma.md:82 references/create-prisma.md:109 references/frameworks.md:127 references/frameworks.md:133 references/frameworks.md:162 references/frameworks.md:169 references/frameworks.md:289 references/frameworks.md:295 references/frameworks.md:127 references/frameworks.md:133 references/frameworks.md:162 references/frameworks.md:169 references/frameworks.md:289 references/frameworks.md:295 references/sdk-api.md:35 references/sdk-api.md:47 references/sdk-api.md:35 references/sdk-api.md:47 references/sdk-api.md:47 references/sdk-api.md:48 references/sdk-api.md:58 references/troubleshooting.md:333 references/troubleshooting.md:333 references/troubleshooting.md:187 references/troubleshooting.md:191 references/troubleshooting.md:197 references/troubleshooting.md:216 references/troubleshooting.md:244 SKILL.md:129 SKILL.md:129 SKILL.md:148 SKILL.md:147 SKILL.md:191
📁 Filesystem access (5)
references/compute-config.md:141 references/compute-config.md:149 references/frameworks.md:359 references/frameworks.md:379 references/troubleshooting.md:371
⚙️ External commands (50)
SKILL.md:3 SKILL.md:18-23 SKILL.md:23-25 SKILL.md:25 SKILL.md:29-31 SKILL.md:31-34 SKILL.md:34-36 SKILL.md:36 SKILL.md:42 SKILL.md:43 SKILL.md:53-55 SKILL.md:55 SKILL.md:56-59 SKILL.md:59-60 SKILL.md:60-61 SKILL.md:61-62 SKILL.md:62-67 SKILL.md:67-70 SKILL.md:70-73 SKILL.md:73-76 SKILL.md:76-79 SKILL.md:79-82 SKILL.md:82-88 SKILL.md:88-89 SKILL.md:89-90 SKILL.md:90-91 SKILL.md:91-92 SKILL.md:92-93 SKILL.md:93-94 SKILL.md:94-95 SKILL.md:95-101 SKILL.md:101-102 SKILL.md:102 SKILL.md:103 SKILL.md:104-105 SKILL.md:105 SKILL.md:106 SKILL.md:110 SKILL.md:111 SKILL.md:112 SKILL.md:113 SKILL.md:114 SKILL.md:115 SKILL.md:116 SKILL.md:117 SKILL.md:121 SKILL.md:122 SKILL.md:123 SKILL.md:124-128 SKILL.md:128
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/prisma-prisma-compute/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/prisma-prisma-compute/security.svg)](https://skillstore.io/skills/prisma-prisma-compute?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/prisma-prisma-compute?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-compute/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/prisma-prisma-compute.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

prisma. (2026). prisma-compute security audit report (audit version 7) [Author version 1.4.1]. Skillstore. https://skillstore.io/skills/prisma-prisma-compute/audits/7

BibTeX citation

@techreport{prisma-prisma-prisma-compute-2026, author = {prisma}, title = {prisma-compute security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/prisma-prisma-compute/audits/7}, note = {Author version 1.4.1} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "prisma-compute security audit report (audit version 7)" version: "1.4.1" type: report authors: - name: "prisma" date-released: "2026-07-23" url: "https://skillstore.io/skills/prisma-prisma-compute/audits/7" identifiers: - type: other value: "skillstore:prisma-prisma-compute:audit:7" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
45
Architecture
100
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Prepare Framework Deployment

Check a Hono, NestJS, or Bun application for correct entrypoint, host, port, and environment settings.

Operate Preview and Production Releases

Select projects, branches, environment roles, deployment targets, verification steps, promotion, and rollback commands.

Build Platform Automation

Use Compute SDK and Management API guidance to design authenticated deployment tooling with redacted outputs.

Try These Prompts

Check Deployment Readiness 
Assess this Prisma project for Compute readiness. Identify its framework, entrypoint, port, host binding, environment source, and safest next step.
Create Compute Configuration 
Create or update prisma.compute.ts for this application. Preserve existing behavior, avoid secret values, and explain each deployment default.
Diagnose a Failed Deployment 
Troubleshoot this failed Prisma Compute deployment. Inspect build output, authentication context, branch scope, logs, host binding, and port configuration.
Design Monorepo Delivery 
Design a non-interactive deployment workflow for this monorepo. Include target selection, preview isolation, secret handling, verification, promotion, rollback, and failure reporting.

Best Practices

  • Inspect existing scripts, configuration, framework output, and CLI help before changing deployment behavior.
  • Confirm workspace, project, branch, environment role, and production intent before any remote mutation.
  • Redact tokens, database URLs, environment values, and signed upload links from logs and summaries.

Avoid

  • Do not use placeholder database URLs or commit secret values into Compute configuration.
  • Do not deploy production changes with confirmation bypasses unless the user explicitly approves the exact target.
  • Do not treat local readiness or build success as proof that public ingress works.

Frequently Asked Questions

Is prisma.compute.ts required?
No. Simple applications can use explicit CLI flags, while reusable defaults and monorepos benefit from a Compute configuration file.
Which frameworks have direct deployment support?
Supported keys include Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, and custom artifacts.
How does the skill authenticate?
It uses existing OAuth sessions or service-token environment variables. It verifies context without printing secret values.
Can it deploy directly to production?
Yes, after explicit production intent. Safer workflows build an unpromoted candidate, verify its public URL, then promote it separately.
Does deployment run database migrations?
No. Deployments do not run migrations, seed data, or schema push. Run the project's approved database workflow separately.
What deployment failures can it diagnose?
It checks build artifacts, authentication, branch scope, environment scope, runtime logs, public URLs, host binding, and deployed ports.

Developer Details

Author

prisma

License

MIT

Author version

v1.4.1

Skillstore revision

r2

Repository

https://github.com/prisma/skills/tree/1a9f427e9fe2137298abbcc1a6f372db92e8c40d/prisma-compute

Ref

ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006

Maintenance freshness

7/25/2026

Usage

0 downloads · 0 views

File structure

📁 references/

📄 app-deploy-cli.md

📄 compute-config.md

📄 create-prisma.md

📄 frameworks.md

📄 sdk-api.md

📄 troubleshooting.md

📄 SKILL.md

More from prisma

View all

Related Skills

View all