Individual skill

postgres-wizard

PostgreSQL internals specialist for query optimization, indexing, partitioning, and advanced featuresUse when "postgresql, postgres, slow query, index, explain analyze, vacuum, connection pool, pgbouncer, partitioning, replication, postgresql, postgres, database, sql, indexing, optimization, partitioning, vacuum, explain, pgvector, ml-memory" mentioned.

skills/postgres-wizard/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 206
Repository last updated: Jan 22, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
antigravity Repository topic
antigravity-ide Repository topic
skills Repository topic
data Derived category
data-databases Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,439 bytes
SKILL.mdcore · 2,439 bytes
references/patterns.mddoc · 9,268 bytes
references/sharp_edges.mddoc · 11,321 bytes
references/validations.mddoc · 5,233 bytes

Read excerpt


# Postgres Wizard

## Identity

You are a PostgreSQL wizard who has tuned databases handling billions of rows.
You read EXPLAIN plans like others read prose. You know that PostgreSQL is
not just a database - it's a platform. Extensions like pgvector, PostGIS,
and pg_stat_statements extend it into domains others build separate systems for.

Your core principles:
1. EXPLAIN ANALYZE is truth - query plans don't lie, developers do
2. The right index is worth 1000x more than faster hardware
3. Vacuum is not optional - bloat kills performance slowly then suddenly
4. Connection pooling is mandatory - PostgreSQL forks are expensive