Database Operations

VerifiedCaution

Manages PostgreSQL database via Prisma for a backend project. Runs actions like migrations, seeding, reset, Prisma Studio, schema inspection, client generation, and status checks. Use when you need to modify or inspect the database, such as applying new migrations or seeding test data.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#database#prisma#postgresql#migrations#docker

Recommended for

Automated summary

Manages PostgreSQL database operations via Prisma including migrations, seeding, schema inspection, and Prisma Studio.

Strengths

  • Automates common database tasks like migrations and seeding
  • Reduces manual Docker commands
  • Safe reset operation with user confirmation
  • Provides schema viewing and client generation

Limitations

  • Requires Docker and the backend container to be running
  • Only works with a specific project setup (local paths)
  • Reset confirms but still drops data without backup
When to use it

Use when you need to run database migrations, seed test data, open Prisma Studio, or inspect the Prisma schema during development.

When not to use it

Do not use for production database operations or when you need to execute raw SQL queries not covered by Prisma.

Security analysis

Caution
Quality score88/100

The skill leverages Bash and Docker to execute Prisma commands directly inside a running container. While all actions are legitimate database operations, the use of docker exec and argument interpolation poses a risk if inputs are not carefully controlled. The reset action highlights a destructive operation but is gated by a confirm step.

Findings
  • •Uses docker exec to run arbitrary commands inside a container, which could be exploited if arguments are not sanitized.
  • •The reset action is destructive (drops all data) but includes user confirmation instruction.
How this analysis is made

Examples

Run pending migrations
Run the pending database migrations.
Seed test data
Seed the database with test data.
Open Prisma Studio
Open Prisma Studio to browse the database visually.

name: db description: Database operations - run migrations, seed data, open Prisma Studio, reset, or inspect schema. Use when the user needs to work with the database. argument-hint: [action] allowed-tools: Bash, Read disable-model-invocation: true

Database Operations

Manage the PostgreSQL database via Prisma. All commands target the backend at C:/Users/pi/projects/rea/main/backend.

Parse $ARGUMENTS for the action.

Actions

migrate (default)

Run pending migrations against the local database.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npx prisma migrate deploy"

migrate:dev

Create a new migration during development.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npx prisma migrate dev --name $ARGUMENTS[1]"

Requires a migration name as the second argument.

seed

Seed the database with test data.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npm run db:seed"

reset

Reset the database (drops all data, re-runs migrations and seed). Confirm with user before running.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npx prisma migrate reset --force"

studio

Open Prisma Studio for visual database browsing.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npx prisma studio"

Note: Prisma Studio runs on port 5555 inside the container. The user may need to map this port.

schema

Display the current Prisma schema. Read the file: C:/Users/pi/projects/rea/main/backend/prisma/schema.prisma

generate

Regenerate the Prisma client after schema changes.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npx prisma generate"

status

Show migration status.

docker exec rea-backend sh -c "cd /home/site/wwwroot && npx prisma migrate status"

Notes

  • The database container must be running (docker-compose up -d db)
  • Connection string: postgresql://dev:dev@db:5432/realestate (inside Docker network)
  • Adminer UI available at http://localhost:8080 (server: db, user: dev, pass: dev, db: realestate)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/database-operations-mm5t8bbg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/database-operations-mm5t8bbg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/database-operations-mm5t8bbg/download' --output '.skill-downloads/database-operations-mm5t8bbg/SKILL.md.part' && mv '.skill-downloads/database-operations-mm5t8bbg/SKILL.md.part' '.skill-downloads/database-operations-mm5t8bbg/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/database-operations-mm5t8bbg/SKILL.md' && test -s '.skill-downloads/database-operations-mm5t8bbg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/db' && cp -R '.skill-downloads/database-operations-mm5t8bbg' '.claude/skills/db'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/database-operations-mm5t8bbg'

openskills read 'database-operations-mm5t8bbg'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/database-operations-mm5t8bbg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills