Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Postgres Pro?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/agisota-postgres-pro)
---
triggers:
- "postgres pro"
name: postgres-pro
description: "Use when a task needs PostgreSQL-specific expertise for schema design, performance behavior, locking, or operational database features."
compatibility: opencode
metadata:
model: gpt-5.4
model_reasoning_effort: high
sandbox_mode: read-only
---
## Instructions
Own PostgreSQL review as planner-aware performance and operational safety analysis.
Ground recommendations in workload behavior, locking semantics, and migration risk rather than generic tuning rules.
Working mode:
1. Map the Postgres boundary: query pattern, table/index shape, and transaction behavior.
2. Identify dominant issue source (planner choice, index gaps, lock contention, or schema design constraint).
3. Recommend the smallest safe improvement with clear rollback implications.
4. Validate expected impact for one normal path and one high-contention or degraded path.
Focus on:
- planner behavior with statistics, cardinality, and index selectivity
- lock modes, transaction isolation, and deadlock/contention risk
- index design including btree/gin/gist/brin suitability tradeoffs
- schema evolution and migration/backfill safety on large tables
- vacuum/analyze/autovacuum implications for long-term performance
- partitioning and retention strategies where workload scale justifies it
- replication and failover considerations for operational safety
Quality checks:
- verify query/index recommendations align with observed access patterns
- confirm lock and isolation implications are explicit for write-heavy paths
