Prisma ORM schema design, migrations, client generation, and query patterns. Use when designing database schemas, writing migrations, querying data, or managing Prisma Client.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 clearly identifies the technology (Prisma ORM), lists specific capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. It is concise, uses third-person voice, and is distinctive enough to avoid conflicts with other database-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' are highly specific and unlikely to conflict with generic database or other ORM skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured Prisma skill that provides concrete, executable guidance with good workflow clarity including validation checkpoints for migrations. The content is concise and respects Claude's intelligence. The main weakness is the reference to REFERENCE.md which cannot be verified as it's not included in the bundle.
Suggestions
Include the referenced REFERENCE.md in the bundle or inline the most critical query patterns (singleton client, basic CRUD) to ensure the skill is self-sufficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Prisma is or how ORMs work, assumes Claude's competence, and every section delivers actionable information without padding. The best practices section is tightly written with Prisma-specific gotchas rather than generic advice. | 3 / 3 |
Actionability | Provides fully executable commands, a complete copy-paste-ready schema example with realistic models and relations, and specific migration commands. The guidance is concrete throughout—specific CLI commands, real Prisma schema syntax, and explicit rules rather than vague descriptions. | 3 / 3 |
Workflow Clarity | The migration workflow section provides a clear 4-step sequence with explicit validation checkpoints: generate SQL → inspect for destructive operations → test on local DB and revert if failures → deploy in CI and assert clean application. This is a proper validate → fix → retry feedback loop for a potentially destructive operation. | 3 / 3 |
Progressive Disclosure | References REFERENCE.md for query patterns and CRUD examples, and database-config.md for project-specific details, which is good structure. However, REFERENCE.md is not provided in the bundle, making it impossible to verify the reference is valid. The skill itself is well-organized with clear sections but the missing bundle file is a concern. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%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.
cc13aaf
Table of Contents
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.