postgres
PostgreSQL best practices, query optimization, connection troubleshooting, and performance improvement. Load when working with Postgres databases.
90
63%
Does it follow best practices?
Impact
93%
1.43xAverage score across 17 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/postgres/SKILL.mdQuality
Discovery
67%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 its domain (PostgreSQL) and provides an explicit 'when to use' clause, which is good. However, the capability descriptions are category-level rather than concrete actions, and the trigger terms could be expanded to cover more natural user phrasings. It would benefit from more specific actions and additional keyword variations to improve selection accuracy.
Suggestions
Replace category-level terms with concrete actions, e.g., 'Analyzes slow queries with EXPLAIN, recommends indexing strategies, configures connection pooling, and resolves common Postgres errors.'
Expand trigger terms to include common variations users would say: 'pg', 'psql', 'slow query', 'database indexing', 'connection pool', 'SQL performance', '.sql files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PostgreSQL) and several action areas (best practices, query optimization, connection troubleshooting, performance improvement), but these are category-level rather than concrete specific actions like 'rewrite slow queries using EXPLAIN ANALYZE' or 'configure connection pooling'. | 2 / 3 |
Completeness | Clearly answers both 'what' (PostgreSQL best practices, query optimization, connection troubleshooting, performance improvement) and 'when' ('Load when working with Postgres databases') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'PostgreSQL' and 'Postgres databases' as natural keywords, plus 'query optimization' and 'connection troubleshooting', but misses common user variations like 'slow query', 'pg', 'psql', 'database performance', 'indexing', 'EXPLAIN', or '.sql'. | 2 / 3 |
Distinctiveness Conflict Risk | PostgreSQL is a specific technology which helps distinctiveness, but terms like 'query optimization' and 'performance improvement' could overlap with general database skills or MySQL/other DB skills. The 'best practices' term is quite broad and could conflict with general coding skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels as a well-organized reference index with excellent progressive disclosure and conciseness. However, it lacks any actionable content in the body itself — no code examples, no troubleshooting steps, no quick-start guidance. It functions more as a table of contents than a skill, leaving Claude entirely dependent on following external links to perform any task.
Suggestions
Add a 'Quick Start' or 'Common Tasks' section with 2-3 concrete, executable examples (e.g., a connection string template, a basic query optimization command like EXPLAIN ANALYZE, or a common troubleshooting step)
Add a brief workflow or decision tree for common scenarios (e.g., 'When troubleshooting slow queries: 1. Check pg_stat_statements → 2. Run EXPLAIN ANALYZE → 3. See indexing.md for index improvements')
Include at least one inline code snippet for the most common task (e.g., connection setup or basic query pattern) so Claude has immediately actionable guidance without needing to fetch a reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean — it's essentially a well-organized index/table of contents with no unnecessary explanation. Every token serves a navigational purpose. No concepts are over-explained. | 3 / 3 |
Actionability | The skill provides clear navigation to reference materials but contains no executable code, commands, or concrete examples in the body itself. It's a directory rather than actionable guidance — Claude must follow links to get actual instructions. The 'Use for' column helps but doesn't constitute concrete guidance. | 2 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. For a skill covering query optimization, connection troubleshooting, and performance improvement, there are no steps for how to approach these tasks, no validation checkpoints, and no decision trees for which reference to consult when. | 1 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md is a clean overview organized into three logical sections (Generic Postgres, Operations/Architecture, PlanetScale-Specific) with well-signaled one-level-deep references. Each reference file is clearly labeled with its use case. | 3 / 3 |
Total | 9 / 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.
- Repository
- planetscale/database-skills
- Commit
b156f4c
- 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.