CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

neon-postgres

Configure Prisma for Neon with connection pooling.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/neon-postgres/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body reads as a lean pattern reference with correct core facts (pooled URL for the client, direct URL for migrations, PgBouncer limits), but it is not actionable: no code examples, no ordered setup steps, and the Sharp Edges and When to Use sections are non-informative placeholders. Fixing the placeholder table and adding concrete configuration examples would most improve it.

Suggestions

Replace the placeholder Sharp Edges table ("Issue | high | See docs") with real issues and concrete solutions, e.g. prepared-statement errors under PgBouncer transaction mode resolved via pgbouncer: true in the Prisma datasource block.

Add executable examples: a schema.prisma datasource block showing url = env("DATABASE_URL") and directUrl = env("DIRECT_URL"), plus example env values with the Neon -pooler suffix.

Remove the boilerplate "When to Use" sentence referencing a nonexistent overview and replace it with genuine applicability guidance (e.g., when to choose neon-http vs neon-serverless for Drizzle).

DimensionReasoningScore

Conciseness

The Patterns sections are lean bullet lists with no over-explanation of concepts Claude already knows, but the eight identical placeholder rows ("Issue | high | See docs") and the boilerplate "When to Use" sentence are wasted tokens. This matches "efficient with minor instances that could be trimmed", not 5, because the filler sections mean not every token earns its place.

4 / 5

Actionability

There is no code, no commands, and no example connection strings; guidance like "Use two connection strings: DATABASE_URL: Pooled connection for Prisma Client / DIRECT_URL: Direct connection for Prisma Migrate" is a high-level hint missing the specifics to execute, and the Sharp Edges table provides no actual solutions. It is not 3 because nothing in the body is executable or copy-paste ready, and not 1 because the env-var names and their roles are concrete hints.

2 / 5

Workflow Clarity

Configuration guidance is scattered as unordered pattern fragments: there is no sequence (no steps for obtaining the two URLs, configuring schema.prisma, or running migrations) and no validation checkpoints for database operations; "the workflow or actions described in the overview" references an overview that does not exist. It is not 3 because even a rough ordered sequence is absent, and not 1 because the content is coherent and the pooled-vs-direct distinction is clearly stated.

2 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Patterns subsections, Sharp Edges, When to Use) and no bundle files to disclose. It is not 5 because "See docs" in the Sharp Edges table is a dangling reference pointing to no actual document, and "described in the overview" points to a nonexistent section.

4 / 5

Total

12

/

20

Passed

Description

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

The description is concise and names a concrete, well-scoped task, but it is a single bare sentence: no "when to use" guidance and few natural trigger synonyms (Postgres, PgBouncer, serverless). It would benefit most from an explicit Use-when clause and broader trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up Prisma with a Neon Postgres database, or when users mention Neon, PgBouncer, or hitting database connection limits."

Include natural synonyms and technical trigger terms users would actually say: "Neon Postgres", "serverless Postgres", "DATABASE_URL/DIRECT_URL", "PgBouncer".

Mention the key capabilities covered (connection pooling setup and direct-connection migration wiring) so the "what" is more comprehensive.

DimensionReasoningScore

Specificity

"Configure Prisma for Neon with connection pooling" names the domain (Prisma, Neon, pooling) and a single concrete action, matching the anchor for 1-2 concrete actions that are not comprehensive. It is not 4 because only one action is listed, and not 2 because the action is concrete rather than generic.

3 / 5

Completeness

The description gives a clear "what" (configure Prisma for Neon with pooling) but has no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is not 2 because the "what" is concrete and clear, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Prisma", "Neon", "connection pooling"), but common natural variations are missing: users would say "Neon Postgres", "serverless database", "PgBouncer", or "DATABASE_URL". This matches the anchor for some relevant keywords missing variations, not 4, where keyword coverage is good with only a few terms missing.

3 / 5

Distinctiveness Conflict Risk

"Prisma for Neon" defines a clear niche with only minor overlap risk against generic Prisma or database-configuration skills. It is not 5 because no distinct trigger phrases are articulated, weakening differentiated triggering.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/neon-postgres/SKILL.md

Reviewed

Table of Contents

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.