postgres
PostgreSQL best practices, query optimization, connection troubleshooting, and performance improvement. Load when working with Postgres databases.
Install with Tessl CLI
npx tessl i github:planetscale/database-skills --skill postgresOverall
score
60%
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/skillEvaluation — 96%
↑ 1.32xAgent success when using this skill
Validation for skill structure
Discovery
57%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately identifies PostgreSQL as its domain and lists relevant capability areas, making it distinguishable from other skills. However, it relies on category labels rather than concrete actions, and the trigger guidance is too generic to help Claude confidently select this skill in ambiguous situations. The description would benefit from more specific actions and richer trigger terms.
Suggestions
Replace category labels with specific actions: 'Analyze and optimize slow PostgreSQL queries, diagnose connection pool issues, tune pg_stat configurations, write efficient indexes'
Expand trigger terms to include natural user phrases: 'Use when user mentions Postgres, psql, pg_ functions, slow database queries, connection timeouts, or SQL performance issues'
Add explicit trigger scenarios: 'Use when troubleshooting database connection errors, optimizing query execution plans, or configuring PostgreSQL settings'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PostgreSQL) and lists several action areas (best practices, query optimization, connection troubleshooting, performance improvement), but these are category labels rather than concrete specific actions like 'analyze slow queries' or 'configure connection pooling'. | 2 / 3 |
Completeness | Has a 'what' (PostgreSQL best practices, optimization, troubleshooting) and a 'when' clause ('Load when working with Postgres databases'), but the when clause is generic and doesn't provide explicit trigger scenarios like 'when user mentions slow queries' or 'connection errors'. | 2 / 3 |
Trigger Term Quality | Includes 'PostgreSQL' and 'Postgres databases' as natural keywords users might say, but misses common variations like 'psql', 'pg_', 'SQL queries', 'database performance', or 'slow queries' that users would naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | PostgreSQL/Postgres is a specific technology that clearly distinguishes this from other database skills (MySQL, MongoDB, etc.) and general coding skills. The focus on this specific database system creates a clear niche. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
45%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a well-organized index/table of contents rather than actionable guidance. While the progressive disclosure and conciseness are excellent, the complete absence of any executable examples, troubleshooting workflows, or concrete instructions means Claude would need to fetch external references for any actual task. The skill description promises 'query optimization, connection troubleshooting, and performance improvement' but delivers only links.
Suggestions
Add a 'Quick Start' section with 2-3 common executable queries (e.g., checking slow queries, connection status, index usage)
Include a troubleshooting workflow with explicit steps: diagnose -> identify cause -> apply fix -> verify
Add at least one concrete example for each major category (e.g., a sample EXPLAIN ANALYZE interpretation, a connection pooling configuration snippet)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean - pure reference table format with no unnecessary explanation. Assumes Claude knows what Postgres concepts are and just needs to know where to find detailed guidance. | 3 / 3 |
Actionability | Contains no executable code, commands, or concrete guidance - only links to external references. The skill itself provides no actionable instructions, just a directory of where to look. | 1 / 3 |
Workflow Clarity | No workflow or process guidance whatsoever. For a skill covering query optimization and troubleshooting, there's no sequence of steps, no validation checkpoints, and no guidance on how to approach problems. | 1 / 3 |
Progressive Disclosure | Excellent organization with clear one-level-deep references. Well-structured tables with topic, reference link, and use-case descriptions make navigation easy. Content is appropriately split across reference files. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.