Back to catalog
Human reviewedData & analysis

Skill dossier

postgres-pro

Source declaration

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 author's original description, preserved in English. It describes intent, not verified performance.

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

datareferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A PostgreSQL Skill for query optimization with EXPLAIN (ANALYZE, BUFFERS), index design, JSONB, VACUUM tuning and replication monitoring.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Analyzes slow queries using pg_stat_statements and EXPLAIN (ANALYZE, BUFFERS).
  • Designs indexes (B-tree, GIN, GiST, BRIN) and verifies the planner uses them.
  • Uses CREATE INDEX CONCURRENTLY to avoid table locks.
  • Monitors autovacuum, bloat and replication lag via pg_stat views.

Limitations & scope

  • Needs database access; the file targets PostgreSQL 12-16.
  • Extension, replication and maintenance details live in separate reference files.
  • Performance impact is not measured here.

Relevant for

  • Backend developers tuning slow queries
  • DBAs managing replication and vacuum
  • SREs monitoring database health

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
51.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/postgres-pro/references/extensions.mdReference9.4 KB
skills/postgres-pro/references/jsonb.mdReference8 KB
skills/postgres-pro/references/maintenance.mdReference11.8 KB
skills/postgres-pro/references/performance.mdReference6.9 KB
skills/postgres-pro/references/replication.mdReference9.8 KB
skills/postgres-pro/SKILL.mdInstruction5.9 KB

SKILL.md frontmatter

{
  "name": "postgres-pro",
  "description": "Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "infrastructure",
    "triggers": "PostgreSQL, Postgres, EXPLAIN ANALYZE, pg_stat, JSONB, streaming replication, logical replication, VACUUM, PostGIS, pgvector",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "database-optimizer, devops-engineer, sre-engineer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze performance

    Run EXPLAIN (ANALYZE, BUFFERS) to identify bottlenecks.

  2. 02
    Action

    Optimize queries

    Rewrite inefficient queries and run ANALYZE to refresh statistics.

  3. 03
    Decision

    Verify before deploying

    Choose index types by workload and verify with EXPLAIN before deploying.

  4. 04
    Output

    Deliver with evidence

    Provide queries with EXPLAIN output, index rationale, config changes and monitoring queries.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

112 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

100 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 100 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

File deletion is described or implemented

2 occurrences

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

4 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Run EXPLAIN ANALYZE, index builds and VACUUM on a non-production copy first, since they execute queries and add load.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/postgres-pro # .claude/skills/postgres-pro
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/postgres-pro/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to tune a slow query and confirm it runs EXPLAIN (ANALYZE, BUFFERS) before and after creating an index.

Prerequisites

  • Needs database access; the file targets PostgreSQL 12-16.
  • Extension, replication and maintenance details live in separate reference files.
  • Performance impact is not measured here.

Example prompts

Representative task

Using the postgres-pro skill, find the slowest queries in pg_stat_statements, analyze the orders query with EXPLAIN (ANALYZE, BUFFERS), propose a concurrent partial index and verify the planner uses it.

Inspect before use

Read the postgres-pro skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/postgres-pro/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Gives an end-to-end slow-query to fix to verification example.
  • Requires verifying index use before and after changes.

Considerations

  • EXPLAIN ANALYZE actually executes the query, so use care with writes.
  • Index and VACUUM changes affect live systems.
Research conclusion

A verification-first guide for PostgreSQL tuning and operations.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/postgres-pro
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.