skilld
All skills
prisma avatar

/prisma-postgres-setup

@b491588 official
by prismaprisma/skills66 stars
7

Obtain or reuse a Prisma Postgres database and connect an application. Use for "set up Prisma Postgres", "connect my app to Prisma Postgres", or Prisma Postgres setup in v0 and Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; honors an explicit driver, alternative ORM, or database-only choice.

Ask your Agent

Use this Skill: https://skilld.dev/gh/prisma/skills/prisma-postgres-setup

This session only. Nothing lands on disk.

SKILL.md

≈85 tokens always: the name and description. ≈847 when used: this file. ≈2.1k more on demand in 3 files.

Prisma Postgres setup

Connect the intended database, then verify it from the application. Keep provisioning separate from ORM configuration so an existing database is reused.

1. Inspect the project

Check the user's requested ORM or driver, installed packages, database connection, and environment-loading files. Check secret presence without printing values.

  • Honor explicit choices such as Drizzle, pg, or database-only setup.
  • For query or schema work in an already configured app, use its version-matched ORM guidance; do not restart setup.

2. Reuse or obtain a database

Situation Action
Existing connection or connected integration Verify its project, database, and environment; reuse it.
v0 or Vercel Marketplace Read Marketplace setup and use the native integration flow.
Standalone persistent database Read provisioning; use an authenticated CLI, MCP tool, Console, or Management API.
Temporary development database requested Read the create-db section in provisioning, including expiry and claiming.

Resolve the workspace, project, and region before creation. If several resources fit, ask which one to use. If provisioning is blocked by permissions or quota, report the blocker; do not delete another resource or switch workspaces to get around it.

3. Connect the application

Use the connection appropriate to the chosen driver and runtime. Store it in the project's secret environment configuration, never source code or chat. Preserve unrelated entries, update the intended variable once, and ensure local secret files are ignored by Git.

Application processes and CLI commands may load different environment files. For example, a framework may load .env.development.local while a shell command does not. A variable missing from the shell does not mean the database is missing: load the intended file for that command without displaying credentials, and do not provision another database.

4. Configure the ORM and verify

For Prisma ORM setup, load prisma-orm-setup using the host's skill loader or read its installed SKILL.md. If it is not installed, obtain it from prisma/skills. It owns ORM version selection and configuration. If that handoff is unavailable, report it.

For an explicitly selected alternative, keep that ORM or driver and use its documented setup. For database-only setup, stop after verifying connectivity.

Run a read-only query against the intended database through the application's chosen ORM or driver. Report what was connected, the selected ORM/version, and the query result without secrets. If any step is blocked or untested, say so instead of claiming setup is complete.

For Studio, SDK integrations, or database operations beyond initial setup, read operations.

Source: SKILL.md on GitHub

Third-party checks

No alertstoday4 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill is a database setup utility authored by Prisma. It follows security best practices by instructing the agent to handle credentials securely, avoid logging secrets, and utilize official vendor tools and repositories. The external resources and packages identified are all official Prisma-owned assets.

  • Sockettoday

    No alerts

  • Snyktoday

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at b491588. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago

Capability

metadata
{
  "author": "prisma",
  "version": "2.0.0"
}

Topics

  • Database
  • prisma
  • postgres
  • provisioning
  • management-api
  • connection-string
  • nodejs

README badge

README badge for prisma/skills/prisma-postgres-setup

What it does

Provisions a new Prisma Postgres database via the Management API and configures it in a local Node.js project with Prisma 7. Handles service token authentication, region selection, project creation, schema definition, and end-to-end connection verification.

Generated from the current SKILL.md.

Frequently asked

Does this skill work with existing databases, or only new ones?
This skill provisions new Prisma Postgres databases via the Management API. For existing databases that are already connected, use standard Prisma CLI tasks (schema/migration work). For CI/CD preview databases or multi-tenant setups, use the dedicated skills `prisma-postgres-cicd` or `prisma-postgres-integrator`.
What authentication does this require?
You need a workspace service token from Prisma Console (Workspace Settings > Service Tokens). The skill checks for the token in your initial prompt, the PRISMA_SERVICE_TOKEN environment variable, or `.env` file before asking you to create one.
Does this set up Prisma 7?
Yes. The skill installs `@prisma/adapter-pg` (Prisma 7's driver adapter for direct PostgreSQL), creates `prisma.config.ts` for Prisma 7 configuration, and ensures connection URLs are managed there instead of in the schema.
What happens if I hit my database limit?
The skill lists your existing projects as an interactive menu, lets you pick one to delete, then retries the creation.
Does this create migration files?
Yes. When you define or confirm your schema, the skill runs `npx prisma migrate dev --name init`, which generates migration files in `prisma/migrations/` and the Prisma client in one step. This is required for CI/CD and production deployments.

Generated from the current SKILL.md. These answers refresh after source changes.