Back to catalog
Human reviewedData & analysis

Skill dossier

database-optimizer

Source declaration

Optimizes database queries and improves performance across PostgreSQL and MySQL systems. Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.

The author's original description, preserved in English. It describes intent, not verified performance.

Optimizes database queries and improves performance across PostgreSQL and MySQL systems. Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.

datareferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Optimizes slow PostgreSQL and MySQL queries by capturing a baseline with EXPLAIN ANALYZE, changing one thing at a time, and comparing before and after.

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

  • Captures baseline metrics and execution plans before any change.
  • Identifies inefficient queries, missing indexes and configuration issues.
  • Designs index strategies, including CREATE INDEX CONCURRENTLY on PostgreSQL, and query rewrites.
  • Validates results by re-running EXPLAIN ANALYZE and documenting before and after metrics.

Limitations & scope

  • Covers PostgreSQL and MySQL only; other engines are out of scope.
  • Needs access to a database and extensions such as pg_stat_statements, which this review did not test.
  • Index and config suggestions depend on your data and workload; none are verified here.

Relevant for

  • Developers investigating slow queries
  • DBAs tuning indexes and configuration
  • Teams addressing lock contention

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
54.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/database-optimizer/references/index-strategies.mdReference7.9 KB
skills/database-optimizer/references/monitoring-analysis.mdReference14.3 KB
skills/database-optimizer/references/mysql-tuning.mdReference10.8 KB
skills/database-optimizer/references/postgresql-tuning.mdReference10 KB
skills/database-optimizer/references/query-optimization.mdReference5.7 KB
skills/database-optimizer/SKILL.mdInstruction6.1 KB

SKILL.md frontmatter

{
  "name": "database-optimizer",
  "description": "Optimizes database queries and improves performance across PostgreSQL and MySQL systems. Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.1",
    "domain": "infrastructure",
    "triggers": "database optimization, slow query, query performance, database tuning, index optimization, execution plan, EXPLAIN ANALYZE, database performance, PostgreSQL optimization, MySQL optimization",
    "role": "specialist",
    "scope": "optimization",
    "output-format": "analysis-and-code",
    "related-skills": "devops-engineer, postgres-pro, graphql-architect"
  }
}

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

    Capture baseline

    Capture baseline metrics and run EXPLAIN ANALYZE before any changes.

  2. 02
    Action

    Implement incrementally

    Apply optimizations incrementally with monitoring, validating each change before the next.

  3. 03
    Decision

    Revert on regression

    Test in non-production first and revert if write performance degrades or replication lag increases.

  4. 04
    Output

    Deliver analysis and SQL

    Provide baseline analysis, root causes with EXPLAIN evidence, implementation SQL and validation queries.

Potential risk surfaces

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

Items warrant review

68 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 useNot observed
Note

File modification is described or implemented

63 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 63 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

5 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 5 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 its SQL and index changes in non-production first and review them before touching a production database.

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/database-optimizer # .claude/skills/database-optimizer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/database-optimizer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm database-optimizer/SKILL.md exists at the destination, then ask Claude Code to use the database-optimizer skill on a small test task.

Prerequisites

  • Covers PostgreSQL and MySQL only; other engines are out of scope.
  • Needs access to a database and extensions such as pg_stat_statements, which this review did not test.
  • Index and config suggestions depend on your data and workload; none are verified here.

Example prompts

Representative task

Use the database-optimizer skill to analyze this slow PostgreSQL query on orders and customers, capture EXPLAIN (ANALYZE, BUFFERS) as a baseline, propose one index change and show how to validate it.

Inspect before use

Read the database-optimizer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/database-optimizer/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Requires a measured baseline and one change at a time so impact can be attributed.
  • Explicitly warns about write amplification and replication lag.

Considerations

  • Index creation and config changes can be costly on large production tables.
  • Statistics and vacuum maintenance are ongoing work beyond a single session.
Research conclusion

A measurement-first tuning guide that is only as safe as the non-production testing you do with it.

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/database-optimizer
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.