CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 strong, highly actionable pattern catalog with executable code and well-organized sections. The main gaps are a missing verification checkpoint in the destructive migration workflow and a single-file structure that inlines reference-grade detail.

Suggestions

Add an explicit validation checkpoint in the expand-and-contract migration workflow (e.g., verify the backfill is complete and confirm row counts before creating the NOT NULL constraint migration), since the workflow involves potentially destructive schema changes.

Consider moving the error-code catalog, serverless connection setup, and extended trap details into a references/ file to keep SKILL.md as a lean overview with clearly signaled one-level-deep references.

Trim the version-check blockquote to the essential version-sensitive items to reduce token spend on the most commonly loaded section.

DimensionReasoningScore

Conciseness

Dense tables and BAD/GOOD contrast snippets with no filler or explanation of concepts Claude already knows. The version-check blockquote runs long and the singleton section carries two full init options, so minor trimming is possible — the 4 anchor, not 5.

4 / 5

Actionability

Fully executable throughout: Prisma schema, TS snippets (cursor pagination, P2002/P2025/P2003 error mapping, DTO mapping), and exact CLI commands with flags (migrate dev/deploy/diff). Copy-paste ready and covers the common cases — the 5 anchor.

5 / 5

Workflow Clarity

Multi-step workflows (expand-and-contract migration, dev/deploy split) are clearly sequenced, but the destructive schema-change workflow has no explicit verification between backfill and applying the NOT NULL constraint. Per the rubric cap for destructive/batch workflows lacking validation, this cannot score above 3.

3 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned with clear headers (When to Activate, Core Concepts, Anti-Patterns, Best Practices) and easy navigation. However ~400 lines of reference material (error-code catalog, serverless setup, full trap list) could arguably be split into reference files — the 4 anchor, not 5.

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.

An exemplary description: concrete capability list, named traps that double as distinctive triggers, and an explicit 'Use when' clause covering all major use cases. Only minor headroom on natural-language synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'schema design, query optimization, transactions, pagination' — plus specific traps ('updateMany returning count not records, $transaction timeouts, migrate dev resetting the DB'). Comprehensive coverage with no significant gaps, matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (pattern areas and named traps) and 'when' ('Use when writing a Prisma schema or query, or debugging transactions, migrations, or serverless connection limits') with concrete trigger phrases — the 5 anchor verbatim.

5 / 5

Trigger Term Quality

Good natural keywords: 'Prisma schema or query', 'transactions, migrations', 'serverless connection limits', plus API-specific tokens like updateMany and migrate dev. Not 5 because a few natural variations users might say ('database', 'ORM', 'connection pool') are absent.

4 / 5

Distinctiveness Conflict Risk

'Prisma ORM patterns for TypeScript backends' carves a clear niche; Prisma-specific tokens ($transaction, @updatedAt, migrate dev) make wrong-skill triggering very unlikely. Only trivial overlap with adjacent postgres/migration skills. Third-person voice throughout — no penalty.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/prisma-patterns/SKILL.md

Reviewed

Table of Contents

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.