postgres-pro

Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

86%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.

A well-structured, highly actionable skill body built on executable SQL examples, clear constraints, and a properly layered reference table. The main improvement is tightening a few low-value sections and making the workflow's error-recovery loop explicit.

Suggestions

Trim the 'Senior PostgreSQL expert…' intro line and the bottom 'Knowledge Reference' concept list, which restate what Claude already knows.

Add an explicit validate→fix→retry loop in the Core Workflow (e.g. 'If EXPLAIN still shows a Seq Scan after creating the index, revise the index and re-verify').

Avoid duplicating the description's trigger list in the 'When to Use This Skill' section; reference it instead to save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient concrete SQL and actionable constraints, but the 'Senior PostgreSQL expert…' intro line, the 'When to Use' list echoing the description, and the bottom 'Knowledge Reference' line listing concepts Claude already knows are minor trim candidates.	4 / 5
Actionability	Fully executable, copy-paste-ready SQL throughout — pg_stat_statements query, EXPLAIN (ANALYZE, BUFFERS), CREATE INDEX CONCURRENTLY, GIN index, VACUUM/replication monitoring — plus concrete MUST DO/MUST NOT DO rules covering common cases.	5 / 5
Workflow Clarity	A clear 5-step Core Workflow with explicit verification (Step 4 'Verify the index is used', before/after EXPLAIN), but the validate→fix→retry feedback loop is implied rather than spelled out, which keeps it just below a 5 for these database/batch operations.	4 / 5
Progressive Disclosure	A concise overview body points to five well-signaled one-level-deep references via a 'Load When' table; all referenced files (performance, jsonb, extensions, replication, maintenance) exist in ./references/, giving clean navigation.	5 / 5
	Total	18 / 20 Passed

Description

88%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 strong, specific description that clearly states capabilities and when to invoke the skill, using third-person imperative voice throughout. The only weakness is trigger-term synonym coverage, which could add 'Postgres', 'indexes', and 'pg_stat'.

Suggestions

Add synonym trigger terms users naturally say, e.g. 'Postgres' (not just 'PostgreSQL'), 'indexing', 'pg_stat views', and '.sql files'.

Consider mentioning 'index design' explicitly among the concrete actions, since it is a core capability.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'optimizing PostgreSQL queries', 'configuring replication', 'EXPLAIN analysis', 'JSONB operations', 'extension usage', 'VACUUM tuning', 'performance monitoring' — covering the domain comprehensively.	5 / 5
Completeness	Explicitly answers both what and when with concrete trigger phrases via 'Use when optimizing PostgreSQL queries, configuring replication…' and 'Invoke for EXPLAIN analysis, JSONB operations…'.	5 / 5
Trigger Term Quality	Strong natural keywords a user would say ('EXPLAIN analysis', 'JSONB', 'VACUUM', 'replication'), but missing common synonyms/variations like 'Postgres' shorthand, 'indexes', 'pg_stat', or '.sql'.	4 / 5
Distinctiveness Conflict Risk	A clear PostgreSQL niche with distinct triggers (EXPLAIN, JSONB, VACUUM), but 'optimizing PostgreSQL queries' carries minor overlap risk with a generic database-optimizer skill.	4 / 5
	Total	18 / 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: jeffallan/claude-skills
Path: skills/postgres-pro/SKILL.md
Commit: 882ef55

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