prisma-database

Prisma ORM schema design, migrations, client generation, and query patterns. Use when designing database schemas, writing migrations, querying data, or managing Prisma Client.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable rules-and-gotchas reference with executable commands, copy-paste code, and specific failure modes. Its one weakness is workflow clarity: destructive database operations lack an integrated validation checkpoint and feedback loop — 'prisma validate' is buried in an 'Other commands' list rather than sequenced into the migration workflow.

Suggestions

Add a numbered migration workflow with an explicit validation checkpoint, e.g.: 1. Edit schema 2. `npx prisma validate` 3. Fix errors and re-validate 4. `npx prisma migrate dev` 5. `npx prisma generate`.

Turn the 'inspect migration.sql before applying' rule into a feedback loop: if destructive operations (drops, column rewrites) are found, add the backfill step, regenerate, and re-inspect before applying.

Promote `prisma validate` out of the trailing 'Other commands' line into the Migration rules section as a required pre-apply step so the destructive-operation safeguard is impossible to miss.

Dimension	Reasoning	Score
Conciseness	The body is lean bullets and one copy-paste snippet; it assumes Claude's Prisma competence and adds only non-obvious rules ("Never edit an already-applied migration file — the checksum is recorded and will fail", "db push skips migration history entirely — prototyping only"). No padding found; every token earns its place.	5 / 5
Actionability	Fully executable guidance throughout: exact commands ("npx prisma migrate dev ... in development only — never in production", "npx prisma migrate deploy", "npx prisma generate after every schema change"), concrete decorators (@@index, @relation onDelete: Cascade, @map/@@map), a copy-paste PrismaClient singleton snippet, and a specific error code (P2002) with handling direction. Covers the common cases; matches the level-5 anchor.	5 / 5
Workflow Clarity	Migration rules imply a sequence (inspect migration.sql before applying; generate after every schema change) but no explicit validate→fix→retry loop exists for these destructive database operations. Per the rubric's cap ("database operations ... missing feedback loops cap workflow_clarity at 3"), this cannot score above 3: "prisma validate" appears only in the trailing 'Other commands' line, not as an integrated checkpoint. Not level 2 because the destructive-op safeguards (never edit applied migrations, inspect before applying, dev/deploy split) are real and well-stated.	3 / 5
Progressive Disclosure	The body is under 50 lines with no external references needed and no bundle files (references/, scripts/, assets/ are absent), so the simple-skill exception applies: well-organized sections (Migration rules, Schema gotchas, Client and queries) plus one-level pointers to project config and docs earn a 5.	5 / 5
	Total	18 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third person, concise, with an explicit 'Use when' clause listing concrete triggers and a specific multi-action capability list anchored on the distinct 'Prisma' keyword. The only gap is a few natural trigger variations such as the schema.prisma file reference.

Dimension	Reasoning	Score
Specificity	"Prisma ORM schema design, migrations, client generation, and query patterns" lists multiple specific concrete actions covering the full Prisma workflow. It matches the level-5 anchor (comprehensive, multi-action coverage) rather than level 4, since no core Prisma task category is omitted.	5 / 5
Completeness	Explicitly answers both: what ("Prisma ORM schema design, migrations, client generation, and query patterns") and when ("Use when designing database schemas, writing migrations, querying data, or managing Prisma Client") with concrete trigger phrases. Clear level-5 match; not 4 because the 'when' clause is already explicit and specific.	5 / 5
Trigger Term Quality	Good natural-term coverage: "Prisma", "database schemas", "migrations", "querying data", "Prisma Client". Not level 5 because common variations users say are missing (e.g., ".prisma"/"schema.prisma" file references, "database" as a standalone trigger, "ORM" beyond the single mention).	4 / 5
Distinctiveness Conflict Risk	"Prisma" is a clear niche trigger making it mostly distinct from other skills. Minor overlap risk remains: "designing database schemas" and "querying data" could collide with generic SQL/database skills when Prisma is not named. Not 5 for that residual overlap; clearly above level 3.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/prisma/SKILL.md
Commit: c0f4566

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.