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.
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clearly identifies its niche (Neon serverless Postgres with Vercel), lists specific capabilities and integrations, and provides explicit trigger conditions including common error scenarios. The description uses proper third-person voice and includes both platform-specific terms and error conditions that users would naturally mention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: 'HTTP/WebSocket connections, database branching (git-like), Drizzle/Prisma ORM integration, migrations, PITR backups' plus specific error scenarios. | 3 / 3 |
Completeness | Clearly answers both what ('Neon + Vercel serverless Postgres for edge and serverless environments') and when ('Use for Cloudflare Workers, Vercel Edge, Next.js apps...') with explicit trigger scenarios including error conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '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 targets Neon serverless Postgres with Vercel integration, edge environments, and specific error types - unlikely to conflict with general database or other Postgres skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, highly actionable skill with excellent progressive disclosure and clear workflows. The main weakness is moderate verbosity - redundant explanations of pooled connections, marketing-style production metrics, and a checklist that largely duplicates earlier content. The code examples are production-ready and the error catalog references are well-organized.
Suggestions
Remove the 'Production Example' section with marketing metrics (50K+ requests, 100K+ users) - this doesn't help Claude execute tasks
Consolidate the repeated pooled connection warnings into a single prominent callout rather than mentioning it in Quick Start, Critical Rules, and the checklist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally 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 earlier content. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples for both Neon and Vercel Postgres, complete with TypeScript imports, template tag syntax, and transaction handling. The configuration files are copy-paste ready with specific version numbers. | 3 / 3 |
Workflow Clarity | Clear sequential setup process (Choose Platform → Get Connection String → Query Database), explicit validation checkpoints in the checklist, and proper error handling patterns shown in transaction examples with try/finally blocks for connection release. | 3 / 3 |
Progressive Disclosure | Excellent structure with a quick start section followed by clear 'When to Load References' guidance pointing to one-level-deep reference files (setup-guide.md, error-catalog.md, common-patterns.md, advanced-topics.md). Each reference is clearly signaled with specific use cases. | 3 / 3 |
Total | 11 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
90d6bd7
Table of Contents
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.