postgres

PostgreSQL best practices, query optimization, connection troubleshooting, and performance improvement. Load when working with Postgres databases.

Quality

70%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/postgres/SKILL.md

Quality

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.

This description adequately identifies the PostgreSQL domain and provides an explicit 'when' clause, which is good. However, the capabilities listed are high-level categories rather than specific concrete actions, and the trigger terms could be expanded to capture more natural user language variations like 'slow queries' or 'connection pool'.

Suggestions

Replace category-level terms with specific concrete actions (e.g., 'Analyze slow queries, configure indexes, troubleshoot connection pool issues, optimize JOIN performance').

Expand trigger terms in the 'Load when' clause to include natural variations like 'psql', 'slow queries', 'database connections', 'SQL performance', or 'pg_stat' to improve matching.

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-level rather than concrete specific actions like 'analyze slow queries' 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', 'Postgres', and 'databases' which are relevant keywords, but misses common variations users might say like 'SQL queries', 'psql', 'database performance', 'slow queries', or 'connection errors'.	2 / 3
Distinctiveness Conflict Risk	Specific to PostgreSQL which helps distinguish from general database skills, but 'query optimization' and 'performance improvement' could overlap with other database-related skills (MySQL, general SQL optimization skills).	2 / 3
	Total	9 / 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 skill excels as a well-organized reference index with excellent conciseness and progressive disclosure. However, it lacks actionable content in the main body - no quick-start examples, common commands, or troubleshooting steps that Claude could immediately use. The skill would benefit from a brief 'Quick Start' section with common operations before the reference tables.

Suggestions

Add a 'Quick Start' section with 2-3 common executable examples (e.g., connection string format, basic query optimization check, common troubleshooting command)

Include a brief workflow section for common scenarios like 'Debugging slow queries: 1. Check ps-insights → 2. Review query-patterns → 3. Apply indexing recommendations'

Add a few inline code snippets for the most frequent operations (e.g., EXPLAIN ANALYZE usage, connection pooling configuration example)

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations of what Postgres is or how databases work. Every line serves a purpose - either providing a recommendation or directing to specific reference material.	3 / 3
Actionability	The skill is primarily a reference index pointing to other files rather than providing direct executable guidance. While the table structure is clear, there's no concrete code, commands, or examples in the main skill body itself.	2 / 3
Workflow Clarity	The tables organize topics well but don't provide any workflow sequencing. For a skill covering optimization and troubleshooting, there's no guidance on which references to consult first or how to approach common scenarios step-by-step.	2 / 3
Progressive Disclosure	Excellent progressive disclosure structure. Clear overview with well-organized tables pointing to one-level-deep references. Topics are logically grouped (Generic Postgres, Operations/Architecture, PlanetScale-Specific) with clear 'Use for' descriptions.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: 23 days ago

Table of Contents

Discovery Implementation Validation

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.