neon-vercel-postgres
Neon + Vercel serverless Postgres for edge and serverless environments. Use for Cloudflare Workers, Vercel Edge, Next.js apps with HTTP/WebSocket connections, database branching (git-like), Drizzle/Prisma ORM integration, migrations, PITR backups, or encountering connection pool exhausted errors, TCP connection issues, SSL config problems.
82
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/neon-vercel-postgres/skills/neon-vercel-postgres/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly identifies its niche (Neon serverless Postgres), lists concrete capabilities and integrations, and provides explicit trigger conditions including common error scenarios. The description is concise yet comprehensive, covering platforms, tools, features, and troubleshooting use cases. It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: HTTP/WebSocket connections, database branching, Drizzle/Prisma ORM integration, migrations, PITR backups, and specific error troubleshooting scenarios. | 3 / 3 |
Completeness | Clearly answers both 'what' (Neon + Vercel serverless Postgres for edge/serverless environments) and 'when' with explicit triggers via the 'Use for...' clause listing specific scenarios including platforms, features, and error conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Neon', 'Vercel', 'serverless Postgres', 'Cloudflare Workers', 'Vercel Edge', 'Next.js', 'Drizzle', 'Prisma', 'connection pool exhausted errors', 'TCP connection issues', 'SSL config problems'. These are highly specific terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Neon-specific Postgres in serverless/edge contexts. The combination of Neon, Vercel, specific ORMs, and specific error types makes it very unlikely to conflict with generic database or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionability with real, executable code examples and outstanding progressive disclosure with clearly signaled reference files. However, it is severely bloated with redundant information—connection pooling warnings, SSL requirements, and package versions are each repeated multiple times. The workflow could benefit from explicit validation checkpoints between setup steps rather than just a disconnected checklist at the end.
Suggestions
Eliminate redundancy: consolidate the pooled connection string warning, sslmode=require reminder, and package versions to single mentions each—this could cut 30-40% of content.
Remove the 'Never Do' list entirely since it mirrors the 'Always Do' list; or merge them into a single concise table with Do/Don't columns.
Remove the 'Production Example' section (marketing claims about '50K+ daily requests, 0 connection errors' add no actionable value) and the 'Dependencies' section which duplicates the package.json configs above it.
Add a validation step after step 2 (e.g., 'Test connection: `await sql\`SELECT 1\``') to create a proper feedback loop before proceeding to schema creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with significant redundancy. The pooled connection string warning appears 5+ times, sslmode=require is repeated 4+ times, package versions are listed 3 times, and the references section is listed twice. The 'Why this matters' and 'Why these settings' explanations add little value for Claude. The production example section with marketing-style claims ('50K+ daily requests, 0 connection errors') is pure padding. The 'Never Do' list largely mirrors the 'Always Do' list in negated form. | 1 / 3 |
Actionability | Provides fully executable TypeScript code examples for both Neon and Vercel Postgres, including queries, transactions, Cloudflare Worker handlers, Next.js server actions, and Drizzle config. Code is copy-paste ready with proper imports and real patterns. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear 3-step sequence and the setup checklist is comprehensive. However, there are no explicit validation checkpoints in the workflow (e.g., 'verify connection works before proceeding to schema creation'). The checklist at the end is good but disconnected from the setup flow. Migration workflows are deferred entirely to references. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to setup-guide.md, error-catalog.md, common-patterns.md, and advanced-topics.md. The 'When to Load References' section provides clear triggers for loading each reference file. Templates are also clearly cataloged. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.