PostgreSQL patterns for Node.js with pg — connection pooling, parameterized
99
99%
Does it follow best practices?
Impact
100%
1.75xAverage score across 5 eval scenarios
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 a strong skill description that excels across all dimensions. It provides comprehensive specificity with concrete patterns, includes natural trigger terms developers would use, explicitly states both what it does and when to apply it, and has a clearly defined niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: connection pooling, parameterized queries, transactions, BIGINT/NUMERIC type handling, PostgreSQL error code handling, bulk inserts with unnest, and production hardening (SSL, keepAlive, graceful shutdown). | 3 / 3 |
Completeness | Clearly answers both what (PostgreSQL best practices covering specific patterns) AND when ('must be applied by default in every Node.js application using the pg client', 'Always apply these patterns when creating or modifying any Node.js service that connects to PostgreSQL'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'PostgreSQL', 'Node.js', 'pg client', 'connection pooling', 'parameterized queries', 'transactions', 'SSL', 'bulk inserts'. Good coverage of technical terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Node.js + PostgreSQL + pg client. The combination of technology stack (Node.js), database (PostgreSQL), and specific client library (pg) creates clear boundaries unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates best practices for technical documentation. It provides comprehensive, production-ready patterns for PostgreSQL with Node.js while maintaining excellent token efficiency. The content assumes Claude's competence, provides fully executable code examples, includes clear validation steps (checklist, error handling patterns), and organizes information for easy navigation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly efficient with minimal fluff. It jumps straight into executable code examples without explaining what PostgreSQL or connection pooling is. Every section provides actionable patterns without unnecessary preamble. | 3 / 3 |
Actionability | Excellent executable code throughout - complete TypeScript examples for connection pooling, queries, transactions, bulk inserts, and error handling. All code is copy-paste ready with proper imports and real-world patterns. | 3 / 3 |
Workflow Clarity | Multi-step processes like transactions clearly show the BEGIN/COMMIT/ROLLBACK sequence with explicit error handling and the critical finally block for client release. The checklist at the end provides validation checkpoints for implementation. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Connection Pool, Queries, Transactions, etc.) that can be navigated independently. The References section provides one-level-deep links to external documentation for deeper dives. Content is appropriately inline for a comprehensive skill file. | 3 / 3 |
Total | 12 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents