postgres-best-practices

Postgres performance optimization and best practices. Use when writing or reviewing SQL queries, designing schemas, configuring connection pooling, fixing N+1 queries, creating indexes, implementing row-level security, diagnosing slow queries with EXPLAIN ANALYZE, or optimizing database performance.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary progressive-disclosure index: lean, well-categorized, with all referenced files present and complete. Its weak spot is workflow clarity — it routes Claude to the right reference but provides no explicit decision sequence or validation checkpoint, which matters for database operations.

Suggestions

Add a short 'How to apply' workflow with an explicit sequence (e.g. 1. identify the slow query, 2. run EXPLAIN ANALYZE, 3. match symptoms to the relevant rule category, 4. apply the correct pattern, 5. re-run EXPLAIN ANALYZE to verify) so Claude has a validated loop rather than only a catalog.

Include one inline minimal example (e.g. the EXPLAIN ANALYZE before/after for missing-index) in the body so the single most common case is actionable without opening a reference file.

Add a brief validation checkpoint note in 'How to Use' reminding Claude to verify any schema/index change with EXPLAIN ANALYZE before considering it done, addressing the database-operations feedback-loop gap.

Dimension	Reasoning	Score
Conciseness	The body is a lean index — a priority table and one-line rule summaries with no explanation of concepts Claude already knows (no 'what an index is' padding); every line earns its place, matching the 5 anchor.	5 / 5
Actionability	Provides concrete routing guidance: each rule is named, one-line-described, and filed under a prioritized category, and the listed reference files (verified present) hold executable incorrect/correct SQL plus EXPLAIN output. Sits below 5 only because the body itself contains no inline executable SQL example — the executable detail is delegated one level deep.	4 / 5
Workflow Clarity	The priority table implies a critical-to-incremental ordering and 'How to Use' says to read files as needed, but there are no explicit workflow steps or validation checkpoints; given this skill touches database operations, the absence of any validate/verify checkpoint caps it at 3 rather than 4.	3 / 5
Progressive Disclosure	Clean overview/index with 31 rules split across 8 categorized reference files exactly one level deep, all referenced paths verified to exist (every query-/conn-/security-/schema-/lock-/data-/monitor-/advanced- prefix maps to a real file), with well-signaled navigation — matches the 5 anchor.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description: third-person, concrete, and explicit about both capabilities and trigger conditions with strong Postgres-specific keywords. The only minor gap is a few common synonym terms a user might naturally say.

Dimension	Reasoning	Score
Specificity	Names the domain (Postgres performance optimization) and lists many concrete actions across categories — 'designing schemas', 'configuring connection pooling', 'fixing N+1 queries', 'creating indexes', 'implementing row-level security', 'diagnosing slow queries with EXPLAIN ANALYZE' — giving comprehensive coverage; not the 4 anchor because there are no meaningful coverage gaps.	5 / 5
Completeness	Explicitly answers both 'what' ('Postgres performance optimization and best practices') and 'when' with a concrete 'Use when...' clause enumerating trigger scenarios, matching the 5 anchor closely; not 4 because the 'when' is explicit and specific rather than merely present.	5 / 5
Trigger Term Quality	Strong natural keywords users would say ('SQL queries', 'N+1 queries', 'indexes', 'connection pooling', 'EXPLAIN ANALYZE', 'database performance') with some synonyms, but a few common variations are absent (e.g. 'slow query', 'query tuning', 'vacuum', 'bloat'), so it sits just below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Postgres-specific niche with distinct triggers (RLS, EXPLAIN ANALYZE, N+1, connection pooling) and minimal overlap risk with other skills; the third-person voice is correct.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: provectus/awos-recruitment
Path: registry/skills/postgres-best-practices/SKILL.md
Commit: 298fce7

Reviewed: 4 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.