agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/postgres-pro/SKILL.md

postgres-pro

Skill3 starsChanged 9 months agoMITView on GitHub

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

15 other projects use a version of this, 13 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ui-ux-pro-max.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 5 are common, 5 are distinctive, and 0 are very specific to this project.

  • 5

    Common

    Most of the 14 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Analyze performance: - Use EXPLAIN ANALYZE, pg_stat_statements

    line 36
  2. Distinctive:

    Use EXPLAIN ANALYZE for query optimization

    line 57
  3. Distinctive:

    Create appropriate indexes (B-tree, GIN, GiST, BRIN)

    line 58
  4. Distinctive:

    Update statistics with ANALYZE after bulk changes

    line 59
  5. Common:

    Use connection pooling (pgBouncer, pgPool)

    line 61
  6. Common:

    Use prepared statements to prevent SQL injection

    line 64
  7. Common:

    Create indexes without analyzing query patterns

    line 68
  8. Common:

    Use SELECT * in production queries

    line 69
  9. Distinctive:

    Use text for UUID storage (use uuid type)

    line 72
  10. Common:

    When implementing PostgreSQL solutions, provide:

    line 78

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

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

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Performancereferences/performance.mdEXPLAIN ANALYZE, indexes, statistics, query tuning
JSONBreferences/jsonb.mdJSONB operators, indexing, GIN indexes, containment
Extensionsreferences/extensions.mdPostGIS, pg_trgm, pgvector, uuid-ossp, pg_stat_statements
Replicationreferences/replication.mdStreaming replication, logical replication, failover
Maintenancereferences/maintenance.mdVACUUM, 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:

  1. Query with EXPLAIN ANALYZE output
  2. Index definitions with rationale
  3. Configuration changes with before/after values
  4. Monitoring queries for ongoing health checks
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free