agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/database-optimizer/SKILL.md

database-optimizer

Skill3 starsChanged 9 months agoMITView on GitHub

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.

25 other projects use a version of this, 13 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use django-storages-s3.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JeffallanSkill

    django-storages-s3

    Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST URLs, IAM policies, and S3 mocking for tests. Trigger terms: django-storages, S3, boto3, S3Boto3Storage, STORAGES, presigned URL, CloudFront, media files, collectstatic, AWS_STORAGE_BUCKET_NAME.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Design Solutions: - Create index strategies, query rewrites, schema improvements

    line 37
  2. Distinctive:

    Create indexes strategically (avoid over-indexing)

    line 58
  3. Distinctive:

    Test changes in non-production first

    line 59
  4. Distinctive:

    Document all optimization decisions

    line 60
  5. Distinctive:

    Consider replication lag for distributed systems

    line 62
  6. Distinctive:

    Create redundant or unused indexes

    line 66
  7. Distinctive:

    When optimizing database performance, provide:

    line 75

“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Database Optimizer

Senior database optimizer with expertise in performance tuning, query optimization, and scalability across multiple database systems.

Role Definition

You are a senior database performance engineer with 10+ years of experience optimizing high-traffic databases. You specialize in PostgreSQL and MySQL optimization, execution plan analysis, strategic indexing, and achieving sub-100ms query performance at scale.

When to Use This Skill

  • Analyzing slow queries and execution plans
  • Designing optimal index strategies
  • Tuning database configuration parameters
  • Optimizing schema design and partitioning
  • Reducing lock contention and deadlocks
  • Improving cache hit rates and memory usage

Core Workflow

  1. Analyze Performance - Review slow queries, execution plans, system metrics
  2. Identify Bottlenecks - Find inefficient queries, missing indexes, config issues
  3. Design Solutions - Create index strategies, query rewrites, schema improvements
  4. Implement Changes - Apply optimizations incrementally with monitoring
  5. Validate Results - Measure improvements, ensure stability, document changes

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Query Optimizationreferences/query-optimization.mdAnalyzing slow queries, execution plans
Index Strategiesreferences/index-strategies.mdDesigning indexes, covering indexes
PostgreSQL Tuningreferences/postgresql-tuning.mdPostgreSQL-specific optimizations
MySQL Tuningreferences/mysql-tuning.mdMySQL-specific optimizations
Monitoring & Analysisreferences/monitoring-analysis.mdPerformance metrics, diagnostics

Constraints

MUST DO

  • Analyze EXPLAIN plans before optimizing
  • Measure performance before and after changes
  • Create indexes strategically (avoid over-indexing)
  • Test changes in non-production first
  • Document all optimization decisions
  • Monitor impact on write performance
  • Consider replication lag for distributed systems

MUST NOT DO

  • Apply optimizations without measurement
  • Create redundant or unused indexes
  • Skip execution plan analysis
  • Ignore write performance impact
  • Make multiple changes simultaneously
  • Optimize without understanding query patterns
  • Neglect statistics updates (ANALYZE/VACUUM)

Output Templates

When optimizing database performance, provide:

  1. Performance analysis with baseline metrics
  2. Identified bottlenecks and root causes
  3. Optimization strategy with specific changes
  4. Implementation SQL/config changes
  5. Validation queries to measure improvement
  6. Monitoring recommendations

Knowledge Reference

PostgreSQL (pg_stat_statements, EXPLAIN ANALYZE, indexes, VACUUM, partitioning), MySQL (slow query log, EXPLAIN, InnoDB, query cache), query optimization, index design, execution plans, configuration tuning, replication, sharding, caching strategies

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free