← MCP server and skill grades

skills

prisma/skills

B
Type
Skill
Scanned
Nov 13, 2026
Version
a6f192959cf4
Files read
83

This project is an official collection of Markdown instruction files (skills) that teach AI coding agents how to set up, query, upgrade, and deploy applications using Prisma ORM, Prisma Postgres, and Prisma Compute. It contains no executable code of its own, and the biggest risk is that the Compute skill instructs the agent to send CLI error messages to Prisma via npx prisma feedback without asking the user first.

What it can reach

Shell commands
Guides the coding agent to run Prisma CLI, npm/npx, Vercel CLI, and application build commands in the terminal.
Files
Guides the coding agent to read and modify application code, Prisma schemas, migration folders, prisma.config.ts, .gitignore, and GitHub Actions workflows.
Secrets
Guides the coding agent to inspect environment variable files (.env) and configure database connection URLs and cloud service secrets without printing their values.
Network
Guides the coding agent to connect to databases, provision cloud resources on Prisma and Vercel, fetch sibling skill text, and submit CLI bug reports to Prisma.

Findings

1 medium3 low
  1. MediumAgent instructed to send CLI error messages externally without user consent

    prisma-compute/SKILL.md:123

    When debugging an unresolvable or internal Prisma CLI error, this skill and its debug-deploy-failures.md reference tell the agent to run npx prisma feedback with the first error line automatically, without asking the user for approval first. Database and deployment error lines can inadvertently include internal hostnames, file paths, project names, or credentials the AI fails to recognize as secrets, and allowlisting npx prisma commands also gives a prompt-injected agent a sanctioned way to send text off the machine.

    Fix: Require explicit user confirmation and show the exact message to the user before running npx prisma feedback.

  2. LowUnpinned runtime package execution via npx -y @latest

    prisma-postgres-setup/references/provisioning.md:10

    Several instructions tell the agent to download and run floating @latest npm packages at runtime (such as npx -y @prisma/cli@latest, npx create-db@latest, and npx create-prisma@latest), using -y to skip npm's installation prompt. Although other skills in this repository warn against floating @latest tags, running unpinned packages with -y bypasses project lockfiles and would automatically execute compromised code if an upstream package were hijacked.

    Fix: Omit -y so package downloads require confirmation, and prefer project-pinned CLI dependencies or pinned versions.

  3. LowTroubleshooting guide suggests disabling TLS certificate verification first

    prisma-upgrade-v7/SKILL.md:244

    The first troubleshooting bullet for SSL certificate errors tells the agent to set rejectUnauthorized: false on the database driver adapter (and references/driver-adapters.md repeats this alongside trustServerCertificate: true without a local-only warning). Coding agents fixing connection errors commonly pick the simplest code-only option, which disables TLS certificate validation in production and exposes database credentials and traffic to man-in-the-middle interception.

    Fix: Recommend configuring trusted CA certificates first and explicitly warn the agent never to set rejectUnauthorized: false on production or remote database connections.

  4. LowSkill handoff fetches live instructions from mutable GitHub main branch

    prisma-postgres-setup/SKILL.md:41

    Instead of loading the locally installed sibling skill first, step 4 tells the agent to read prisma-orm-setup/SKILL.md directly from https://github.com/prisma/skills/blob/main/prisma-orm-setup/SKILL.md, and deprecated redirect skills instruct installing missing skills from GitHub without asking the user first. Pulling live instructions from a mutable branch at runtime bypasses the locally installed version the user reviewed.

    Fix: Prefer the locally installed ../prisma-orm-setup/SKILL.md file first, and ask for user confirmation before fetching or installing skills from GitHub.