Agent skill · software engineering · aiskillstore
prisma-postgres-setup
Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to "set up a database", "create a Prisma Postgres project", "get a connection string", "connect my app to Prisma Postgres", or "provision a database".
Why this skill is useful
Adds specific API commands and workflows for provisioning a Prisma Postgres database that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires prisma account access. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Prisma Postgres Setup Procedural skill that guides you through provisioning a new Prisma Postgres database via the Management API and connecting it to a local project. When to Apply Use this skill when: Setting up a new Prisma Postgres database for a project Creating a Prisma Postgres project and connecting it locally Obtaining a connection string for Prisma Postgres Provisioning a database via the Management API (not the Console UI) Do not use this skill when: Setting up CI/CD preview databases — use prisma-postgres-cicd Building multi-tenant database provisioning into an app — use prisma-postgres-integrator Working with a database that already exists and is connected (schema/migration tasks are standard Prisma CLI) Prerequisites Node.js 18+ A Prisma Postgres workspace (create one at https://console.prisma.io if needed) A workspace service token (see references/auth.md) UX Guidelines When presenting choices to the user (region selection, project deletion, etc.), use your platform's interactive selection mechanism (e.g., ask tool in Claude Code, structured prompts in other agents). Do not print static tables and ask the user to type a value — present selectable options so the user can pick with minimal effort. Workflow Follow these steps in order. Each step includes the API call to make and how to handle the response. Step 1: Authenticate You need a service token. Try these methods in order: 1a. Token in the user's prompt Check if the user included a service token in their initial message (e.g., "Set up Prisma Postgres with token eyJ..."). If so, use it exactly as provided — do not truncate, re-encode, or round-trip it through a file. Store it in a shell variable for subsequent calls. 1b. Token in the environment Check for PRISMASERVICETOKEN in the environment or .env file. 1c. Ask the user to create one If no token is available, instruct the user: Create a service token in Prisma Console → Workspace Settings → Service Tokens. Copy the token and paste it here. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/prisma-postgres-setup