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?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

This is a solid, well-structured Prisma skill with executable examples, clear migration workflows with validation steps, and appropriate references to external files. Its main weaknesses are minor verbosity in best practices that Claude would already know and an unverifiable reference to REFERENCE.md. Overall it serves as an effective quick-reference guide for Prisma operations.

Suggestions

Trim the 'Schema Best Practices' to only Prisma-specific gotchas that Claude wouldn't already know (e.g., remove generic advice about timestamps and indexes).

Ensure REFERENCE.md exists in the bundle or inline the most critical query patterns to avoid a dead reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with good use of code blocks and concise best practices, but the schema best practices section includes some guidance Claude would already know (e.g., 'include createdAt and updatedAt timestamps for auditability') and the comments in the command list are slightly redundant for an LLM audience.	2 / 3
Actionability	Provides fully executable commands, a complete copy-paste-ready Prisma schema example, and specific migration commands. The guidance is concrete and directly usable rather than abstract.	3 / 3
Workflow Clarity	The migration workflow section provides a clear validate → fix → retry sequence with explicit validation checkpoints (inspect SQL, run tests, revert if failures, assert clean application in CI). The distinction between dev and production commands is clearly stated.	3 / 3
Progressive Disclosure	References REFERENCE.md for query patterns and database-config.md for project-specific details, which is good structure. However, REFERENCE.md is not provided in the bundle, making the reference unverifiable, and the schema design section is fairly long inline content that could potentially be split out.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

This is a strong skill description that concisely covers the key capabilities of Prisma ORM work, uses third-person voice correctly, and includes an explicit 'Use when...' clause with natural trigger terms. It is well-scoped to a specific technology, making it easily distinguishable from other database or ORM-related skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: schema design, migrations, client generation, and query patterns. These are distinct, well-defined capabilities within the Prisma ecosystem.	3 / 3
Completeness	Clearly 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 an explicit 'Use when...' clause.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Prisma', 'ORM', 'schema design', 'migrations', 'client generation', 'query patterns', 'database schemas', 'Prisma Client'. These cover the main terms a developer would use when seeking Prisma help.	3 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Prisma ORM specifically, which is a distinct technology. Terms like 'Prisma Client', 'Prisma ORM', and 'client generation' create a clear niche that is unlikely to conflict with generic database or other ORM skills.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Commit: 7a69a05

Reviewed: about 1 month 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.