domains / families / data / database-optimizer

database-optimizer

combined

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. Expert database optimizer specializing in modern performance

When to use

• 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
• Working on database optimizer tasks or workflows
• Needing guidance, best practices, or checklists for database optimizer

When not to use

• The task is unrelated to database optimizer
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies overlap in scope but disagree on the procedure. Jeffallan/claude-skills provides a concrete, executable workflow (baseline EXPLAIN, incremental changes, specific SQL examples, and strict MUST/MUST NOT constraints). The other two copies (rmyndharis and sickn33) are nearly identical generic capability lists that lack a specific workflow, instead offering broad topic coverage (NoSQL, Cloud, N+1) and generic instructions. Crowning one would hide the alternative approach of broad capability mapping vs. specific procedural tuning.