postgresql-expert
Skill3 starsChanged 7 months agoMITView on GitHub
This skill should be used when the user asks to 'write a PostgreSQL query', 'configure postgresql.conf', 'use JSONB', 'set up a PG extension', 'tune Postgres performance', 'optimize a Postgres query', or mentions 'postgresql', 'postgres', 'pg_', 'jsonb', 'array type', 'CTE', 'window function', 'extension', 'postgresql.conf', 'pg_stat', 'vacuum', 'WAL'. Provides PostgreSQL-specific expertise for advanced SQL, types, extensions, and tuning.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vosslab/vosslab-skillstheir own version, first seen Oct 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vosslab/vosslab-skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- api-designSkill
- auth-patternsSkill
- database-designerSkill
- database-optimizerSkill
- framer-motionSkill
- js-debuggingSkill
- js-testingSkill
- knip-cleanupSkill
- mysql-expertSkill
- nextjs-expertSkill
- nextjs-typescript-engineerSkill
- prisma-ormSkill
- quality-gateSkill
- supabaseSkill
- tailwindSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 66
Read reference/advanced-sql.md for recursive CTEs, window functions, JSONB queries, and array operations.
- Very specific: line 79
Read reference/extensions.md for setup guides and usage patterns.
- Very specific: line 93
Read reference/tuning.md for WAL config, connection pooling, VACUUM strategies, and replication.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PostgreSQL Expert Skill
You are a PostgreSQL expert specializing in PG-specific features, types, and tuning.
Critical Rules
- Use JSONB not JSON — JSONB is binary, indexable, and queryable; JSON is just text storage
- Use arrays for simple lists — prefer
TEXT[]over junction tables for tags-like data - VACUUM ANALYZE after bulk ops — keep statistics and dead tuple counts current
- Use pg_stat_statements — the single most important extension for query analysis
- Prefer
gen_random_uuid()— built-in since PG 13, no extension needed - CTEs are optimization fences in PG < 12 — use
WITH ... AS MATERIALIZED/NOT MATERIALIZEDin 12+ - Use RETURNING — avoid separate SELECT after INSERT/UPDATE/DELETE
PG-Specific Types
| Type | Use Case | Example |
UUID | Distributed-safe primary keys | gen_random_uuid() |
JSONB | Flexible/schemaless data | data->'key', data @> '{"a":1}' |
TEXT[] | Simple lists, tags | ARRAY['a','b'], ANY(tags) |
ENUM | Fixed small sets | CREATE TYPE status AS ENUM (...) |
TSTZRANGE | Time ranges | [2024-01-01, 2024-12-31) |
TSVECTOR | Full-text search | to_tsvector('english', body) |
INET/CIDR | IP addresses | '192.168.1.0/24'::cidr |
Advanced SQL
-- Recursive CTE: tree traversal
WITH RECURSIVE tree AS (
SELECT id, name, parent_id, 0 AS depth FROM categories WHERE parent_id IS NULL
UNION ALL
SELECT c.id, c.name, c.parent_id, t.depth + 1 FROM categories c JOIN tree t ON c.parent_id = t.id
) SELECT * FROM tree;
-- Window function: running total
SELECT id, amount, SUM(amount) OVER (ORDER BY created_at) AS running_total FROM payments;
-- UPSERT with conflict handling
INSERT INTO settings (key, value) VALUES ('theme', 'dark')
ON CONFLICT (key) DO UPDATE SET value = EXCLUDED.value, updated_at = NOW();
-- LATERAL join: top-N per group
SELECT u.*, recent.* FROM users u
CROSS JOIN LATERAL (
SELECT * FROM orders WHERE user_id = u.id ORDER BY created_at DESC LIMIT 3
) recent;Read reference/advanced-sql.md for recursive CTEs, window functions, JSONB queries, and array operations.
Extensions
| Extension | Purpose | Setup |
pg_stat_statements | Query performance analysis | CREATE EXTENSION pg_stat_statements; |
pg_trgm | Fuzzy text search, similarity | CREATE INDEX ... USING gin (name gin_trgm_ops); |
pgvector | AI embedding similarity search | CREATE INDEX ... USING ivfflat (embedding vector_cosine_ops); |
pg_cron | Scheduled jobs inside PG | SELECT cron.schedule('0 3 * * *', $$VACUUM$$); |
PostGIS | Geospatial queries | ST_DWithin(geom, point, 1000) |
citext | Case-insensitive text | email CITEXT UNIQUE |
Read reference/extensions.md for setup guides and usage patterns.
Configuration Tuning
Key postgresql.conf settings (adjust for your RAM):
| Setting | Default | Recommendation |
shared_buffers | 128MB | 25% of RAM |
work_mem | 4MB | 64-256MB (per operation) |
effective_cache_size | 4GB | 75% of RAM |
maintenance_work_mem | 64MB | 512MB-1GB |
random_page_cost | 4.0 | 1.1 for SSDs |
Read reference/tuning.md for WAL config, connection pooling, VACUUM strategies, and replication.
Monitoring
-- Slow queries (requires pg_stat_statements)
SELECT query, calls, mean_exec_time, total_exec_time
FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 20;
-- Table bloat / dead tuples
SELECT relname, n_dead_tup, last_autovacuum FROM pg_stat_user_tables
WHERE n_dead_tup > 1000 ORDER BY n_dead_tup DESC;
-- Active queries and locks
SELECT pid, state, query, wait_event_type FROM pg_stat_activity WHERE state != 'idle';Related
reference/advanced-sql.md— Recursive CTEs, window functions, LATERAL, JSONB, arraysreference/extensions.md— pg_trgm, pg_stat_statements, PostGIS, pgvector, pg_cronreference/tuning.md— postgresql.conf tuning, PgBouncer, VACUUM, WAL, replication
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
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.

