Tessl • The management layer for AI agent skills

SkillPublic

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

78%

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

Fix and improve this skill with Tessl

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

Quality

Content

72%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, executable reference whose main gaps are structural: no validation checkpoints around destructive database operations (capping workflow clarity) and no progressive disclosure — all specialized patterns are inlined in one monolithic file. Conciseness is good with only minor duplication.

Suggestions

Add explicit validation checkpoints around the destructive workflow, e.g. 'Run npx prisma migrate status before migrate deploy; only reset after confirming no unapplied migrations', turning migrate status into a feedback loop.

Split specialized content into referenced bundle files (e.g. references/nextauth-adapter.md, references/seed.md) and keep SKILL.md as an overview with one-level-deep, clearly signaled links.

Deduplicate the migrate/seed/reset commands between 'Database Initialization' and 'Common Commands', and drop the prerequisites section that repeats the frontmatter compatibility line.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and code with almost no conceptual padding, assuming Claude's competence. Minor duplication — prerequisites repeated from the frontmatter, migrate/seed/reset commands appearing in both 'Database Initialization' and 'Common Commands' — keeps it below the every-token-earns-its-place anchor.	4 / 5
Actionability	Everything is copy-paste ready: install commands, a complete schema.prisma, singleton client, $extends soft-delete pattern, repository functions, idempotent seed script, and package.json seed config, covering the common cases. Not 4: there are no meaningful gaps in executability.	5 / 5
Workflow Clarity	A rough scaffold → migrate → seed sequence is present via the command sections, but workflows involving destructive database operations ('migrate reset — drops and recreates') lack explicit validate-then-proceed checkpoints; 'prisma migrate status' appears only as a bare command, not embedded as a feedback loop. Per the rubric's cap for database operations without validation, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist and the ~390-line body inlines specialized content that clearly belongs in separate reference files (NextAuth adapter models, seed script, repository patterns). Section headers provide structure, so it is above the unstructured-monolith anchor, but nothing is split out or referenced.	3 / 5
	Total	15 / 20 Passed

Description

75%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, third-person description with concrete named deliverables and a clear Prisma niche. Its main weakness is the complete absence of a 'Use when...' trigger clause, which both caps completeness and slightly limits natural trigger coverage.

Suggestions

Append an explicit trigger clause, e.g. 'Use when starting a new Prisma project, writing or editing schema.prisma, creating migrations, or seeding a database.'

Add natural synonyms and file extensions users would mention, such as '.prisma files', 'Prisma ORM', or 'database schema design'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete deliverables — 'schema.prisma (datasource, generator, models, relations, enums), migrations, seed script, Prisma Client usage, type-safe queries, and middleware' — giving comprehensive, specific coverage in third-person voice. No minor gaps in the action list warrant a 4.	5 / 5
Completeness	It clearly answers 'what' (scaffolds a Prisma 6.x project with enumerated components) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Natural terms users would say are present ('Prisma', 'schema.prisma', 'migrations', 'seed script', 'Prisma Client'), but common variations and file extensions ('.prisma', 'ORM', 'database schema') are missing. Good coverage, just shy of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	The Prisma 6.x scaffolding niche is explicit and named, with concrete artifact terms that would not naturally trigger for other database/ORM skills. Minimal conflict risk.	5 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: database/prisma-schema-starter/SKILL.md
Revision: 181fcbc

Reviewed: 7 days ago

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.

prisma-schema-starter

Table of Contents

Is this your skill?