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.
63
75%
Does it follow best practices?
Impact
—
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 both feature-based and error-based scenarios. The inclusion of specific error patterns (connection pool exhausted, TCP issues, SSL config) is particularly effective for routing troubleshooting queries to the right skill.
| 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
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent executable code examples covering multiple platforms and use cases. However, it is severely bloated with redundant information (version numbers repeated 3x, package.json shown 3x, pooling warnings repeated 5+ times) and includes unnecessary explanations that Claude doesn't need. The progressive disclosure structure is well-designed in theory but undermined by inline content that belongs in reference files.
Suggestions
Eliminate redundancy: consolidate version numbers to a single location, show package.json once, and mention the pooled connection string warning once in Critical Rules rather than repeating it throughout.
Remove obvious guidance Claude already knows (never commit .env, use environment variables, handle errors with try/catch) and trim 'Why this matters' / 'Why these settings' explanatory sections.
Add an explicit validation checkpoint after the Quick Start setup (e.g., 'Test connection: run `await sql\`SELECT 1\`` and verify it returns successfully') to improve workflow clarity.
Move the Configuration Files Reference, Dependencies, and Package Versions sections into a reference file since they duplicate information and bloat the main skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Massive redundancy: version numbers repeated 3 times, connection pooling warnings repeated 5+ times, package.json shown 3 times. The 'Why this matters' explanations, 'Why these settings' sections, and 'Production Example' with unverifiable claims all waste tokens. The 'Critical Rules' section has 19 bullet points, many of which are obvious to Claude (e.g., 'never commit .env files', 'use environment variables'). | 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 template tag syntax. | 3 / 3 |
Workflow Clarity | The setup checklist at the end provides a clear sequence, and the Quick Start has numbered steps. However, there are no explicit validation checkpoints within the workflows—no 'verify your connection works' step after setup, no 'run a test query' checkpoint. The migration workflow is deferred entirely to a template file without even a summary. | 2 / 3 |
Progressive Disclosure | References to external files (references/error-catalog.md, references/common-patterns.md, etc.) are well-signaled with clear 'When to Load' guidance. However, no bundle files were provided, so we can't verify these exist. The main file itself is bloated with content that should be in reference files (e.g., full configuration files, dependency lists, version tables repeated multiple times), undermining the progressive disclosure structure. | 2 / 3 |
Total | 8 / 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
5e92b71
- 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.