prisma-patterns

Prisma ORM patterns for TypeScript backends — schema design, query optimization, transactions, pagination, and critical traps like updateMany returning count not records, $transaction timeouts, migrate dev resetting the DB, @updatedAt skipped on bulk writes, and serverless connection exhaustion. Use when writing a Prisma schema or query, or debugging transactions, migrations, or serverless connection limits.

Quality

84%

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

76%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 highly actionable, well-organized body of Prisma patterns with executable BAD/GOOD examples covering the key traps. The main weakness is the destructive migration workflow lacking explicit validation/retry checkpoints, which caps workflow clarity, and a monolithic structure with no external references.

Suggestions

Add an explicit validation/retry checkpoint to the expand-and-contract migration workflow (e.g., verify backfill row counts and run `migrate diff` / a deploy verification after each step) to lift workflow clarity above 3.

Consolidate the repeated adapter-vs-direct PrismaClient initialization hedging into one decision point to reduce conciseness overhead.

Consider extracting the PrismaClient singleton and serverless connection-pool boilerplate into a referenced file (e.g., references/prisma-client.md) and signaling it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean — uses tight tables, BAD/GOOD code pairs, and avoids explaining basic concepts — but the version-check preamble and repeated 'if your Prisma install requires an adapter' hedging across multiple sections add some over-explanation that could be trimmed. Not a 5 due to these padded hedges; not a 3 because the bulk is efficient and assumes Claude's competence.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code for schema, queries, transactions, cursor pagination, soft delete, error handling, and connection pooling, with BAD/GOOD pairs covering the common cases throughout.	5 / 5
Workflow Clarity	The expand-and-contract migration workflow (Step 1/2/3) is sequenced and separates local-vs-deploy, but this destructive/batch workflow lacks explicit validation or verify-after-deploy checkpoints and a validate→fix→retry loop, which the rubric caps at 3 for database operations. The migrate diff drift check exists in a separate section, not embedded in this workflow.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and a single cohesive file, but no bundle files exist (references/scripts/assets absent) and no one-level-deep references are signaled; some boilerplate (singleton, connection-pool setup) could live in a reference file. Not a 5 because references are not signaled and the ~400-line body is monolithic; not a 3 because internal structure is clear and navigable.	4 / 5
	Total	16 / 20 Passed

Description

92%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, specific description that clearly communicates both capabilities and activation triggers, with named non-obvious traps adding high signal. Minor room to broaden trigger-term synonyms for full exhaustiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas ('schema design, query optimization, transactions, pagination') plus five named non-obvious traps ('updateMany returning count not records, $transaction timeouts, migrate dev resetting the DB, @updatedAt skipped on bulk writes, serverless connection exhaustion'), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what it does (pattern and trap list) and when to use it via a concrete 'Use when writing a Prisma schema or query, or debugging transactions, migrations, or serverless connection limits' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('writing a Prisma schema or query,' 'debugging transactions, migrations, or serverless connection limits') with solid keyword coverage, but misses a few common synonyms or file-extension-style variations. Not a 5 because coverage is not exhaustive of all natural phrasings; not a 3 because keyword set is clearly relevant and multi-term.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (Prisma ORM in TypeScript backends) with distinct triggers and named traps unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/prisma-patterns/SKILL.md
Commit: d8409a4

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.