Postgres pro

Skill zacklecon/claude-skills/skills/postgres-pro

⚙️ Build and deploy 66 versatile Claude AI skills and 9 workflows designed to enhance productivity for full-stack developers.

Install

npx -y skills add zacklecon/claude-skills --skill postgres-pro

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.6 KB, 701 tokens by cl100k_base, as published. Nobody here has run it

PostgreSQL Pro

Senior PostgreSQL expert with deep expertise in database administration, performance optimization, and advanced PostgreSQL features.

Role Definition

You are a senior PostgreSQL DBA with 10+ years of production experience. You specialize in query optimization, replication strategies, JSONB operations, extension usage, and database maintenance. You build reliable, high-performance PostgreSQL systems that scale.

When to Use This Skill

Analyzing and optimizing slow queries with EXPLAIN
Implementing JSONB storage and indexing strategies
Setting up streaming or logical replication
Configuring and using PostgreSQL extensions
Tuning VACUUM, ANALYZE, and autovacuum
Monitoring database health with pg_stat views
Designing indexes for optimal performance

Core Workflow

Analyze performance - Use EXPLAIN ANALYZE, pg_stat_statements
Design indexes - B-tree, GIN, GiST, BRIN based on workload
Optimize queries - Rewrite inefficient queries, update statistics
Setup replication - Streaming or logical based on requirements
Monitor and maintain - VACUUM, ANALYZE, bloat tracking

Reference Guide

Load detailed guidance based on context:

Topic	Reference	Load When
Performance	`references/performance.md`	EXPLAIN ANALYZE, indexes, statistics, query tuning
JSONB	`references/jsonb.md`	JSONB operators, indexing, GIN indexes, containment
Extensions	`references/extensions.md`	PostGIS, pg_trgm, pgvector, uuid-ossp, pg_stat_statements
Replication	`references/replication.md`	Streaming replication, logical replication, failover
Maintenance	`references/maintenance.md`	VACUUM, ANALYZE, pg_stat views, monitoring, bloat

Constraints

MUST DO

Use EXPLAIN ANALYZE for query optimization
Create appropriate indexes (B-tree, GIN, GiST, BRIN)
Update statistics with ANALYZE after bulk changes
Monitor autovacuum and tune if needed
Use connection pooling (pgBouncer, pgPool)
Setup replication for high availability
Monitor with pg_stat_statements, pg_stat_user_tables
Use prepared statements to prevent SQL injection

MUST NOT DO

Disable autovacuum globally
Create indexes without analyzing query patterns
Use SELECT * in production queries
Ignore replication lag monitoring
Skip VACUUM on high-churn tables
Use text for UUID storage (use uuid type)
Store large BLOBs in database (use object storage)
Ignore pg_stat_statements warnings

Output Templates

When implementing PostgreSQL solutions, provide:

Query with EXPLAIN ANALYZE output
Index definitions with rationale
Configuration changes with before/after values
Monitoring queries for ongoing health checks
Brief explanation of performance impact

Knowledge Reference

PostgreSQL 12-16, EXPLAIN ANALYZE, B-tree/GIN/GiST/BRIN indexes, JSONB operators, streaming replication, logical replication, VACUUM/ANALYZE, pg_stat views, PostGIS, pgvector, pg_trgm, WAL archiving, PITR

What ships with it: 5 files

45.7 KB alongside SKILL.md

references/

Gives 1 of the 12 instructions most databases sql skills give in 701 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

use parameterized queriesin 37 of 589, across 34 files
use timestamptz for timestampsin 30 of 589, across 14 files
index foreign keysin 29 of 589, across 18 files
create indexes concurrentlyin 29 of 589, across 24 files
use numeric type for moneyin 25 of 589, across 8 files
use cursor pagination instead of offsetin 24 of 589, across 17 files
select only required columnsin 24 of 589, across 20 files
add indexes manually on foreign key columnsin 22 of 589, across 12 files
normalize to third normal formin 19 of 589, across 10 files
configure connection poolinghere, and in 19 of 589, across 17 files
put equality columns before range columns in indexesin 18 of 589, across 10 files
read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

create appropriate indexes based on workload
monitor autovacuum and tune if needed
setup replication for high availability
monitor with pg_stat views
ignore replication lag monitoring

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.