prisma-schema-starter

Scaffold a Prisma 6.x project with schema.prisma (datasource, generator, models, relations, enums), migrations, seed script, Prisma Client usage, type-safe queries, and middleware.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./database/prisma-schema-starter/SKILL.md

Quality

Content

79%

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

This is a high-quality, actionable Prisma starter skill with excellent code examples that are immediately usable. The content is appropriately concise and assumes Claude's competence. However, it could benefit from explicit validation steps in the workflow (especially around migrations) and better progressive disclosure by splitting advanced patterns into referenced files.

Suggestions

Add explicit validation checkpoints after migration commands, e.g., 'Verify migration applied: npx prisma migrate status' with guidance on what to do if it fails

Split NextAuth adapter models and Prisma extensions into separate reference files (e.g., NEXTAUTH.md, EXTENSIONS.md) with clear links from the main skill

Add a rollback/recovery section for when migrations fail or need to be reverted

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context about what Prisma is or how ORMs work.	3 / 3
Actionability	Provides fully executable, copy-paste ready code examples throughout - from schema definitions to repository patterns to seed scripts. Commands are specific and complete with actual flags and options.	3 / 3
Workflow Clarity	Steps are listed clearly (scaffold, migrate, seed) but lacks explicit validation checkpoints. For database migrations which are potentially destructive, there's no feedback loop for verifying migration success before proceeding or rollback guidance if something fails.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic file with no references to external documentation for advanced topics. The NextAuth adapter models and extensions could be split into separate reference files given the skill's length.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 description excels at specificity and distinctiveness, providing comprehensive technical details about Prisma 6.x scaffolding capabilities. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill. The trigger terms are adequate but could include more natural user language variations.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when setting up Prisma, creating database schemas, or when the user mentions Prisma, ORM setup, or database modeling'

Include natural language variations users might say: 'database ORM', 'Prisma setup', 'database schema design', 'TypeScript database'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: scaffold schema.prisma with datasource, generator, models, relations, enums, migrations, seed script, Prisma Client usage, type-safe queries, and middleware. These are all concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with comprehensive capability listing, but lacks an explicit 'Use when...' clause or equivalent trigger guidance to indicate when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes good technical terms like 'Prisma', 'schema.prisma', 'migrations', 'seed script' that users would mention, but lacks common variations like 'ORM', 'database schema', 'Prisma setup', or file extensions like '.prisma'.	2 / 3
Distinctiveness Conflict Risk	Very specific to Prisma 6.x with distinct terminology (schema.prisma, Prisma Client, datasource, generator) that clearly distinguishes it from other database or ORM skills. Unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

Reviewed: 4 months 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.