Content
47%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body has the right conceptual bones (two URLs, driver options, pooler limits) but lacks executable config and a sequenced migration workflow, and it ships empty placeholder content. Replacing the placeholder table and generic When-to-Use with a concrete Prisma datasource example and a step sequence would materially improve it.
Suggestions
Add an executable Prisma `datasource` block showing `DATABASE_URL` (pooled) and `directUrl = env("DIRECT_URL")` so the guidance is copy-paste ready.
Replace the empty Sharp Edges table — name each real issue, severity, and a concrete mitigation instead of 'See docs'.
Lay out a short numbered workflow for applying migrations (set DIRECT_URL, run `prisma migrate`, verify) with an explicit validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient bullet-point prose, but it carries padding with no value: the Sharp Edges table repeats placeholder 'Issue | See docs' rows and the When to Use section is generic filler. | 3 / 5 |
Actionability | It gives concrete specifics (DATABASE_URL pooled for the client, DIRECT_URL direct for migrations, neon-http vs neon-serverless drivers) but no executable Prisma schema datasource block, env example, or connection-string format. | 3 / 5 |
Workflow Clarity | The patterns are listed as disconnected bullets rather than a sequenced workflow, and there are no validation checkpoints despite this touching database migrations. | 2 / 5 |
Progressive Disclosure | The skill is short and organized into clear sections (Patterns, Sharp Edges, When to Use) with no bundle files needed, though the empty placeholder Sharp Edges table is a minor organization gap. | 4 / 5 |
Total | 12 / 20 Passed |