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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill neon-vercel-postgres85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that hits all the marks. It clearly identifies the technology stack (Neon + Vercel serverless Postgres), lists specific use cases and platforms, includes natural trigger terms developers would use, and even anticipates common error scenarios that would lead users to need this skill. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: HTTP/WebSocket connections, database branching, Drizzle/Prisma ORM integration, migrations, PITR backups, and specific error types (connection pool exhausted, TCP connection issues, SSL config problems). | 3 / 3 |
Completeness | Clearly answers both what (serverless Postgres for edge environments with specific features) and when with explicit 'Use for...' clause listing specific scenarios, platforms, and even error conditions that should trigger this skill. | 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 exactly what developers would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically Neon + Vercel serverless Postgres. The combination of platform names (Cloudflare Workers, Vercel Edge), specific ORMs, and unique error types makes it unlikely to conflict with generic database or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and progressive disclosure. The code examples are production-ready and the reference system is well-organized. However, it suffers from some redundancy (repeated pooling warnings, duplicate checklist content) and lacks explicit validation checkpoints in workflows, particularly for database migrations and transaction error recovery.
Suggestions
Remove redundant content: consolidate the 'Critical Rules' and 'Complete Setup Checklist' sections, and reduce repeated warnings about pooled connections to a single prominent callout
Add explicit validation steps to the Quick Start workflow, such as 'Test connection: await sql`SELECT 1`' after setup and verification commands after schema creation
Remove the 'Production Example' section with marketing metrics - it doesn't add actionable value and Claude doesn't need social proof
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the 'Why this matters' explanations, repeated emphasis on pooled connections across multiple sections, and the verbose 'Production Example' section with marketing-style metrics add unnecessary tokens. The checklist at the end largely duplicates the 'Critical Rules' section. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples for both Neon and Vercel Postgres, specific bash commands, complete TypeScript snippets that are copy-paste ready, and concrete configuration files. The template tag syntax examples clearly show correct vs incorrect usage. | 3 / 3 |
Workflow Clarity | While the Quick Start provides a clear 3-step sequence, the skill lacks explicit validation checkpoints. For database operations (migrations, transactions), there's no 'validate -> fix -> retry' feedback loop. The checklist at the end is verification-focused but doesn't integrate into the workflow steps themselves. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear Quick Start overview, 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 explicitly guides when to access deeper content. Templates are appropriately separated. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.