neon-postgres

Configure Prisma for Neon with connection pooling.

Quality

32%

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 ./skills/neon-postgres/SKILL.md

Quality

Content

25%Scale 1-5

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

This skill is a shallow outline that lacks any executable code, concrete examples, or actionable guidance for configuring Prisma with Neon. The sharp edges table is entirely placeholder content with no real issues or solutions filled in. The 'When to Use' section is a tautological filler that adds no value.

Suggestions

Add concrete, copy-paste ready code examples: a schema.prisma datasource block with pooled/direct URLs, a .env file template with actual Neon connection string formats, and a Drizzle setup snippet.

Replace the placeholder sharp edges table with actual issues (e.g., 'Prisma Migrate fails with pooled connection' → 'Use DIRECT_URL in schema.prisma datasource') with real solutions instead of 'See docs'.

Remove the tautological 'When to Use' section and replace it with specific trigger conditions (e.g., 'Use when deploying to serverless platforms like Vercel/Cloudflare Workers with Neon Postgres').

Add a concrete step-by-step workflow with validation: e.g., 1) Set env vars, 2) Configure schema.prisma, 3) Run `npx prisma migrate dev`, 4) Verify connection with `npx prisma db pull`.

Dimension	Reasoning	Score
Conciseness	The content is moderately efficient but includes some unnecessary explanation (e.g., 'Neon provides built-in connection pooling via PgBouncer' is something Claude would know). The sharp edges table is entirely placeholder content with 'Issue' and 'See docs' repeated, which wastes tokens without providing value. The 'When to Use' section is a meaningless tautology.	3 / 5
Actionability	There is no executable code, no concrete configuration examples, no actual connection string formats, no schema.prisma snippets, and no Drizzle setup code. The content only describes what to do at a high level without showing how. The sharp edges table contains only placeholder text ('Issue', 'See docs') with zero actionable information.	1 / 5
Workflow Clarity	There is a rough implied sequence (configure connection strings, use pooled for app, direct for migrations) but no explicit steps, no validation checkpoints, and no error recovery. The workflow is described conceptually rather than as a clear sequence of actions.	2 / 5
Progressive Disclosure	No bundle files are provided, yet the sharp edges table references 'See docs' eight times without any actual links or file paths. The content is structured with headers but lacks any meaningful references or navigation to supporting materials. Content that should be detailed (like actual configuration examples) is neither inline nor referenced.	2 / 5
	Total	8 / 20 Passed

Description

39%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.

The description is very terse—it names a specific technology stack (Prisma, Neon, connection pooling) which gives it reasonable distinctiveness, but it lacks detail about what the configuration involves and provides no 'Use when...' guidance. It would be difficult for Claude to confidently select this skill over related database or ORM skills without more explicit trigger terms and scope definition.

Suggestions

Add a 'Use when...' clause with trigger phrases such as 'Use when the user asks about setting up Prisma with Neon, configuring database connection pooling, or mentions Neon serverless Postgres with Prisma ORM'.

Expand the 'what' with concrete actions, e.g., 'Sets up Prisma schema, configures pooled and direct connection URLs, handles migration setup, and adjusts datasource provider for Neon's serverless Postgres'.

Include additional natural trigger terms and synonyms like 'database', 'Postgres', 'ORM', 'serverless', 'DATABASE_URL', and '.env configuration'.

Dimension	Reasoning	Score
Specificity	Names the domain (Prisma + Neon + connection pooling) but describes only a single generic action ('Configure'). No details about what configuration entails—no mention of schema setup, migration, environment variables, pooler URL formatting, etc.	2 / 5
Completeness	Provides a minimal 'what' (configure Prisma for Neon with connection pooling) but has no 'when' clause at all. The absence of explicit trigger guidance caps this dimension, and the 'what' itself is quite thin.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'Prisma', 'Neon', and 'connection pooling', which are terms users would naturally use. However, it misses synonyms and related terms such as 'database', 'ORM', 'pgbouncer', 'serverless', 'postgres', '.env', or 'DATABASE_URL'.	3 / 5
Distinctiveness Conflict Risk	The combination of Prisma + Neon + connection pooling is fairly niche and unlikely to conflict with most other skills. Minor overlap risk exists with general Prisma configuration or general Neon database skills.	4 / 5
	Total	11 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/neon-postgres/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.